Re: [Puppet-dev] Improve Puppet Server startup time

Are you using a Puppet Server container from https://hub.docker.com/r/puppet/puppetserver? If not, it'd be helpful to know what your Dockerfile is doing. I'm not sure there's been a lot of tuning done for the Puppet Server container we publish. The Puppet Server process itself usually starts in

[Puppet-dev] Re: Accidental Tags deleted from puppetlabs/facter

Actually, it applied to the following repos: facter, puppet, leatherman, pxp-agent, hiera, mcollective. The tags have now been removed. On Mon, Oct 30, 2017 at 4:16 PM Michael Smith <michael.sm...@puppet.com> wrote: > While testing some release automation, tags were accidental

[Puppet-dev] Accidental Tags deleted from puppetlabs/facter

While testing some release automation, tags were accidentally pushed to the https://github.com/puppetlabs/facter repo that were not intended as releases. Given that they were semantically greater than current released versions (978.3 and 978.5) we've deleted them. They were live for ~20 minutes.

[Puppet-dev] Re: Nightly packages (nightlies vs. puppet5-nightly)

On Friday, May 12, 2017 at 1:46:40 AM UTC-7, Dominic Cleal wrote: > > Hello, > > The second half of > > https://puppet.com/blog/full-visibility-and-control-of-your-infrastructure-new-puppet-releases > > talks about prep for Puppet 5 and new nightly packages on > {apt,yum}.puppet.com. I have

Re: [Puppet-dev] freebsd ports provider is broken in puppetlabs/puppet HEAD?

You can run rspec. The standard way to do that for Ruby projects is to run `bundle install`, then `bundle exec rspec spec`. You can also rely on the CI systems on pull requests to check your code, but you'll get faster feedback running locally. On Fri, May 5, 2017 at 2:29 AM

Re: [Puppet-dev] Rebuilding facter...

Unfortunately this is made a little harder since our builds of boost and yaml-cpp aren't hosted. However, the instructions for building them are at https://github.com/puppetlabs/pl-build-tools-vanagon/blob/master/configs/components/boost.rb and

[Puppet-dev] Announce: Puppet Agent 1.6.0 is available

I’m excited to announce a new backwards-compatible feature release for Puppet Agent. The All-in-one Agent package contains updated component versions, including: - Puppet 4.6.0 - this release introduces tooling to support environment isolation, reporting for manual change corrected by

Re: [Puppet-dev] External facts based on OS

about fine-grained differences like between RHEL and >> Debian, then today at least the bash scripts themselves would need to >> contain that logic. >> >> ~Reid >> >> On Wednesday, July 27, 2016 at 5:55:57 PM UTC+1, Michael Smith wrote: >>> >>> There current

Re: [Puppet-dev] External facts based on OS

On Thu, Jul 28, 2016 at 1:25 AM, Reid Vandewiele wrote: > Regardless of the fact that this is on the developer's list, it's worth > mentioning that from a use-case perspective it may not actually be > necessary to worry about that too much. Even though the entire contents of >

Re: [Puppet-dev] External facts based on OS

There currently isn't a way. Since this is the developer's list, I'll go into some details about what would be required for it to work: Currently pluginsync happens before any facts are returned to the system. This makes it difficult to do anything based on OS version. I've had chats about

Re: [Puppet-dev] facter 3, boost, and static libraries

We still compile with -DBOOST_STATIC=ON in several circumstances ( https://github.com/puppetlabs/puppet-agent/blob/master/configs/components/facter.rb#L198), so I'm not sure how you reach that conclusion. However, the note in LTH-74 meant that we would probably switch our packaging (what I linked

Re: [Puppet-dev] puppet error

This is most likely more appropriate for puppet-users. On Tue, Jun 28, 2016 at 4:21 AM, Aditya Gupta wrote: > hello , > > I am getting this error most of the time in puppet client. > > Error: A connection attempt failed because the connected party did not > properly

Re: [Puppet-dev] MCollective and non-root execution

It appeared to me that this > was accomplished by having the config files be 600. > > On Tue, Jun 21, 2016 at 3:25 PM, Michael Smith <michael.sm...@puppet.com> > wrote: > >> There is a section of PE docs that talks about MCollective security as >> setup by PE ( >> https://docs.

Re: [Puppet-dev] MCollective and non-root execution

There is a section of PE docs that talks about MCollective security as setup by PE ( https://docs.puppet.com/pe/latest/orchestration_overview.html#security), as well as points to security notes in the OSS MCollective docs. In short, having the contents of the config files is sufficient to connect

[Puppet-dev] Re: Facter config file

There's some prior art on this question as well: https://projects.puppetlabs.com/issues/11449. It doesn't appear to add anything that wasn't already mentioned here however. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe

Re: [Puppet-dev] Re: Systemd vs RedHat service providers on is-enabled=static

> > > >> I err on providing more feedback when trying to do things that don't make >> sense - like apply Puppet's enable/disable states to a static service - but >> accept that this would make applying the same resource across multiple >> systems difficult. Making it always in-sync would work.

Re: [Puppet-dev] Re: Systemd vs RedHat service providers on is-enabled=static

On Mon, Apr 11, 2016 at 8:35 AM, John Bollinger <john.bollin...@stjude.org> wrote: > > > On Thursday, April 7, 2016 at 1:44:47 PM UTC-5, Michael Smith wrote: >> >> PUP-5353 <https://tickets.puppetlabs.com/browse/PUP-5353> notes an >> inconsistency between t

[Puppet-dev] Systemd vs RedHat service providers on is-enabled=static

the `enable` property of a service that can't be enabled/disabled? -- Michael Smith Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send

Re: [Puppet-dev] Trying to consolidate/batch command execution in a provider

> "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/9D1DB354-8D30-448E-A461-54C67D4B

Re: [Puppet-dev] error when loading functions

> > Corey > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. >

Re: [Puppet-dev] EPP templates and ruby code

15 at 10:41 Martin Alfke <tux...@gmail.com> wrote: > > Hi Michael, > > > > On 10 Sep 2015, at 17:29, Michael Smith <michael.sm...@puppetlabs.com> > wrote: > > > > > Looking at the examples for the 'each' function ( > https://docs.puppetlabs.com/refe

Re: [Puppet-dev] EPP templates and ruby code

Looking at the examples for the 'each' function (https://docs.puppetlabs.com/references/latest/function.html#each) you can replace 'times' with 'each' and I think it'll work. > On Sep 10, 2015, at 4:34 AM, Martin Alfke wrote: > > Hi, > > is there a way to iterate with the

Re: [Puppet-dev] Announce: puppet_agent 0.2.0 released

in the README. Otherwise, I think you'll have many surprised moments going on from your users. Thanks, Trevor On Thu, Jul 23, 2015 at 12:13 PM, Michael Smith michael.sm...@puppetlabs.com wrote: On Thu, Jul 23, 2015 at 6:20 AM, Trevor Vaughan tvaug...@onyxpoint.com wrote: Hi Michael, Does

Re: [Puppet-dev] Announce: puppet_agent 0.2.0 released

3 agents, and confirm that after a successful upgrade they can check back in with the master. Thanks, Trevor On Wed, Jul 22, 2015 at 6:21 PM, Michael Smith michael.sm...@puppetlabs.com wrote: The puppet_agent module 0.2.0 is available. The puppet_agent module is intended to ease

[Puppet-dev] Announce: puppet_agent 0.2.0 released

The puppet_agent module 0.2.0 is available. The puppet_agent module is intended to ease the transition of agents from Puppet 3.8 to Puppet 4 (using the puppet-agent package). It works with both master and master-less setups, but expects your existing Puppet installation to be installed via

[Puppet-dev] PR Triage cancelled July 14th

Due to work on patch releases we're finishing up this week, and lack of activity on a number of PRs we've committed to review, we are cancelling tomorrow's PR triage session for puppet/puppet-server/facter/hiera. We'll resume July 21st. -- Michael Smith Developer, Puppet Labs *PuppetConf 2015

Re: [Puppet-dev] Accessing attribute value of one resource in another resource impleataion

-b43f34c2d859%40googlegroups.com https://groups.google.com/d/msgid/puppet-dev/004da5f1-be9f-4352-a1f8-b43f34c2d859%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Michael Smith Sr. Software Engineer, Puppet Labs *PuppetConf 2015

Re: [Puppet-dev] Calling third party api using puppet

/a38c2d82-ea5f-43a9-bbeb-21c114f9e5f2%40googlegroups.com https://groups.google.com/d/msgid/puppet-dev/a38c2d82-ea5f-43a9-bbeb-21c114f9e5f2%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Michael Smith Sr. Software Engineer

Re: [Puppet-dev] Calling third party api using puppet

this question is that, I have an appliance which exposes RESTful API's and i want to leverage these API's using Puppet. Could you please let me know if there is any such capability? or how i could accomplish this? Thanks! -varun On Thursday, 23 April 2015 09:24:59 UTC-7, Michael Smith wrote: Can

Re: [Puppet-dev] Re: Facter ec2 facts, should they be redone with describe sdk methods

To be clear, my example of iterating over the interfaces was Puppet code. But you can also access the hash from Ruby. New custom facts can be distributed as Puppet modules. See https://docs.puppetlabs.com/guides/plugins_in_modules.html. If you have a concrete set of facts you'd like to propose,

Re: [Puppet-dev] Facter ec2 facts, should they be redone with describe sdk methods

?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Michael Smith Sr. Software Engineer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early

Re: [Puppet-dev] The Road to Facter 3

%40mail.gmail.com https://groups.google.com/d/msgid/puppet-dev/CADWDnrk97Tk8JmFS9hW2bffGj-q%3D-6Z8m%2BmN6_qMAG1%2B66anYw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Michael Smith Sr. Software Engineer, Puppet Labs

[Puppet-dev] Puppet PR Triage

Puppet PR Triage starting in 10 mins at http://links.puppetlabs.com/pr-triage. Preliminary notes at https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-01-21.md Michael Smith Engineer, Puppet Labs -- You received this message because you are subscribed to the Google

Re: [Puppet-dev] Help with mocks / stubs on user provider

This is related to https://github.com/puppetlabs/puppet/pull/3443. The piece that's important here is the definition of #trusted. That may need to be stubbed so that it returns true (or false, it's worth testing both cases in a spec test) to get the behavior you want. One technique we often use

Re: [Puppet-dev] puppet enterprise agent not connect to master

This topic would be more appropriate for the puppet-user mailing list. I'll reply there with some debugging suggestions. On Tue, Dec 23, 2014 at 3:32 AM, Kalai A illiyama...@gmail.com wrote: Hi Recently I moved my server from puppet open source to puppet enterprise. PE master - 3.3.2 PE

Re: [Puppet-dev] PUP-3116 AKA Global Queues

of. On Wed, Dec 17, 2014 at 8:34 PM, Michael Smith michael.sm...@puppetlabs.com wrote: Ok, after some discussions with Josh and Andy (Andy's below), came up with a proposal for how one might write a stash for re-using data. Just for clarification, in what sense do you mean a 'queueing' mechanism

[Puppet-dev] Puppet PR Triage for 2014-12-17 starting soon

Starting the PR triage for puppet/facter/hiera in 5 mins or so at http://links.puppetlabs.com/pr-triage -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to

[Puppet-dev] Re: Puppet PR Triage for 2014-12-17 starting soon

The notes for this week's triage are now available at: *https://github.com/puppet-community/community-triage/blob/master/core/notes/2014-12-17.md https://github.com/puppet-community/community-triage/blob/master/core/notes/2014-12-17.md* On Wed, Dec 17, 2014 at 9:55 AM, Michael Smith michael.sm

Re: [Puppet-dev] PUP-3116 AKA Global Queues

disk I/O. This would be key to getting providers to be able to save state in a non-hacky way as well. Trevor On Tue, Dec 16, 2014 at 6:45 PM, Michael Smith michael.sm...@puppetlabs.com wrote: I don't like any of the ideas I raised, but this will take some digging. We need to determine

Re: [Puppet-dev] PUP-3116 AKA Global Queues

* which is the sad making part :( On Wed, Dec 17, 2014 at 3:53 PM, Michael Smith michael.sm...@puppetlabs.com wrote: I'm doing my own digging to figure out what seems to make sense. Josh had mentioned Puppet::push_context, set in the configurer. We push and pop context for each apply run

Re: [Puppet-dev] PUP-3116 AKA Global Queues

I'm trying to get my head around this, and I don't understand Henrik's worry about unbound class variables causing memory leaks. If you have more background on that, it might help. Avoiding globals in general means you have to have a file on disk. Any of the solutions I can think of to speed that

Re: [Puppet-dev] PUP-3116 AKA Global Queues

AM, Michael Smith michael.sm...@puppetlabs.com wrote: I'm trying to get my head around this, and I don't understand Henrik's worry about unbound class variables causing memory leaks. If you have more background on that, it might help. Avoiding globals in general means you have to have a file

Re: [Puppet-dev] Setting log levels in puppet.conf

I agree, though I like changing the definition of --test to be at least --info instead of exactly (solution 1). It makes the behavior more useful. Sent from my iPad On Nov 4, 2014, at 10:53 PM, David Schmitt da...@dasz.at wrote: On 2014-11-04 22:46, Josh Cooper wrote: Stefan Goethals added