Re: [Puppet Users] Bolt puppetfile install - LFN issue

https://github.com/puppetlabs/r10k/issues/181 seems relevant. It looks like there's a cache_root setting for this that would help, but not clear how to modify it with 'bolt puppetfile install'. On Wed, Feb 12, 2020 at 8:09 AM Andreas Torbiörnsson < andreas.torbiorns...@gmail.com> wrote: > Hi grou

Re: [Puppet Users] Re: puppet bolt templates ??

The existing functions 'epp' and 'inline_epp' work. For example, the following plan returns the resolved template: plan examples::epp() { $templ = @(END) <%= $foo %> END return inline_epp($templ, {'foo' => 'hello'}) } On Tue, Feb 11, 2020 at 10:25 PM Shirish Shukla wrote: > There should be

[Puppet Users] Re: Wash 0.18.0 now available

If you noticed the (very obvious) typo, it's definitely 0.18.0. Oops. On Wed, Jan 15, 2020 at 8:29 AM Puppet Product Updates < puppet-product-upda...@puppet.com> wrote: > Wash 01.8.0 is now available. This release is focused on clarifying some > of the initial interactions with Wash. > > The 'doc

Re: [Puppet Users] Puppet Bolt show diff

The result of an apply statement in a Bolt Plan is a ResultSet (a list of results from each target). The results include the report from applying Puppet, which includes all those details. See https://puppet.com/docs/bolt/latest/applying_manifest_blocks.html#return-value-of-apply-action for how to a

Re: [Puppet Users] Bolt duplicate vagrant nodes issue

The error is because you use the name '127.0.0.1' for two different entries. It needs to be unique in any particular 'nodes' array. One way we commonly fix that is to include the port in the name, so you would have '127.0.0.1:2200' and '127.0.0.1:2201'. This technique is kind of mentioned in the

[Puppet Users] Wash 0.11.0 now available

Wash 0.11.0 is now available. This release added metadata to AWS profiles and improved browsing Kubernetes pods (they now support pods with multiple container instances). See https://github.com/puppetlabs/wash/releases/tag/0.11.0 for more details and fixed issues. Wash 0.10.0 was also released rec

[Puppet Users] Wash 0.9.0 now available

Wash is a shell that helps you manage your remote infrastructure using well-established UNIX-y patterns and tools to free you from having to remember multiple ways of doing the same thing. Wash 0.9.0 is now available. This release added some quality of life improvements, inclu

[Puppet Users] Wash 0.8.1 now available

Wash is a shell that helps you manage your remote infrastructure using well-established UNIX-y patterns and tools to free you from having to remember multiple ways of doing the same thing. Wash 0.8.1 focused on improvements to documentation and usability. We added a friendly p

Re: [Puppet Users] Re: Bolt 1.8.0 now available

Oof, we messed up packaging it. I’ll see about getting a new release out today. On Fri, Jan 4, 2019 at 03:54 wrote: > Hello, > > On Friday, January 4, 2019 at 12:01:58 AM UTC+1, Puppet Product Updates > wrote: >> >> Greetings! >> >> We're happy to announce the release of Bolt 1.8.0. Highlights i

Re: [Puppet Users] Use bolt with existing Puppet manifests

That’s something we intend to work, and I think it will for straight-forward Code setups using Hiera 5. ‘Bolt apply’ let’s you apply a manifest (hasn’t yet been updated to support a site file with node declarations). You can also use ‘apply’ in Bolt Plans to directly apply roles/profiles. The fol

Re: [Puppet Users] Puppet & Ruby gems

I believe http://alcy.github.io/2012/11/21/handling-gem-dependencies-in-custom-puppet-providers/ covers this case. It's old but should still apply. On Mon, Jun 25, 2018 at 6:48 AM Eslam Abd El Naser < eslam.sa3dany2...@gmail.com> wrote: > Hi all, > I'm creating a custom resource type and trying t

Re: [Puppet Users] Re: Puppet certification issue

Puppet uses application-level authentication, not server-level, so a client certificate is not required to connect to the server. Some details about this are documented at https://docs.puppet.com/puppet/5.0/config_file_auth.html and https://docs.puppet.com/puppetserver/5.0/config_file_auth.html.

[Puppet Users] 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 Pu

[Puppet Users] 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 respond after a period of tim

[Puppet Users] Feedback on reporting verbose/debug/show_diff to syslog/eventlog (PUP-6125)

I'd like to solicit feedback on a ticket around changing some behavior in logging when using --verbose, --debug, --test, etc. PUP-6125 points out that --logdest states Where to send log messages. Choose between 'syslog' (the POSIX syslog service), '

Re: [Puppet Users] puppet template syntax problem: undefined method `each' for nil:NilClass

mails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/02e9d496-b1d9-4103-ab44-740ef33172fb%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/02e9d496-b1d9-4103

[Puppet Users] Announce: puppet_agent module 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 package

[Puppet Users] Re: Restricting access to environments by IP or cert in puppetserver

sted). > If, for whatever reason, your choice is to use webrick for your > production, you could work on your "filesterver.conf". This file is > strongly commentend. > > Good luck. > > On Sunday, 15 March 2015 04:24:22 UTC+1, Michael Smith wrote: >> >> Hi,

[Puppet Users] Restricting access to environments by IP or cert in puppetserver

Hi, I'm setting up a puppetserver that will be shared by multiple projects and would like to enforce some control over access to environment resources - particularly puppet:///modules/... file server URLs. The environment name appears at the start of the URL, so with an Apache/Passenger setup

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

If the agent and master have different versions, they're not guaranteed to work together. However, I'm not aware of any specific issues with the combination you have (though our suggested upgrade path is to upgrade the master first; see https://docs.puppetlabs.com/pe/latest/install_upgrading.html).

Re: [Puppet Users] Contributing pieces of a global value from multiple places

On 6/13/2012 4:33 AM, Michael Knox wrote: Hi, I use an augeas resource that manages the FW_CONFIGURATIONS_$zone entry in etc/sysconfig/SuSEfirewall2. augeas {"fwservice_${svc}-$zone": context => "/files/etc/sysconfig/SuSEfirewall2", onlyif=> "match FW_CONFIGURATIONS_$zo

[Puppet Users] Contributing pieces of a global value from multiple places

Hi, I'm using Puppet to configure SuSEfirewall2. I have a class that lets me set a list of ports to open in a variable in /etc/sysconfig/SuSEfirewall2. It's just a wrapper around an Augeas resource. How can I make it so multiple classes can contribute a list of ports to my firewall class? Fo