[Puppet Users] Meet your new Vox Pupuli PMC

['Ben Ford' via Puppet Users]

The 2024 PMC elections have now concluded and it's time to meet your new 
Project Management Committee.

The people on this committee will help take care of the Code of Conduct and its 
values, participate in strategic planning, decision making using lazy 
consensus, accounting, social media and blog post coordination, and so on.

* Alex Fisher (@alexjfisher)
* Tim Muesel (@bastelfreak)
* Ewoud Kohl van Wijngaarden (@ekohl)
* Robert Waffen (@rwaffen)
* Sebastian Rakel (@sebastianrakel)

Let's celebrate all the candidates for running and participating. If you 
weren't selected this year, remember that we have lots and lots of 
opportunities to help out and take on a bigger role in the day to day 
operations. And there's always elections again next year!


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/DD5F397A-3152-4EBD-9EAB-CD3DE37E24C4%40perforce.com.

[Puppet Users] Vox Pupuli Elections closes tomorrow!

['Ben Ford' via Puppet Users]

If you haven’t cast your vote for the PMC 
elections 
yet then you’re running out of time because the election closes tomorrow!

You can still vote until May 15 2024 23:59 
UTC.

Please help us select the Vox Pupuli Project Management Committee for the 2024 
year. The people on this committee will help take care of the Code of Conduct 
and its values, participate in strategic planning, and decision making using 
lazy consensus, amongst other things.

New this year, we are also adding two specialized roles:

  *   The accounting officer will keep track of budget, expenses, and 
sponsorships.
  *   The social media officer will coordinate social, blog, and other similar 
activities. They’re not necessarily responsible for -all- content, but will 
help facilitate it.

These roles will be self selected amongst the committee after the election 
concludes.

Visit the page below to read more about the candidates and to make your choices.

  *   Vox Pupuli elections, 
2024

Thank you so much for your help!


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/FC19559F-8991-4C15-A427-83F1F21D1E2F%40perforce.com.

Re: [Puppet Users] Re custom fact query

['Ben Ford' via Puppet Users]

Hi Dave!

This bug was actually just fixed in 
https://github.com/puppetlabs/facter/pull/2705

For now, you'll need to compare to the downcased version of the string and I'll 
file a ticket to get that noted in docs.

Good luck!



On May 8, 2024, at 2:15 AM, daveford...@gmail.com  
wrote:

You don't often get email from davefordtestt...@gmail.com. Learn why this is 
important

To clarify, tried this on various systems - facter 4.4.0 and ruby 3.0.2 on 
Ubuntu Mint and facter 4.7.0 and ruby 3.1.4 on gentoo.  Examples taken from the 
puppet documentation on writing custom facts.
On Wednesday 8 May 2024 at 10:12:31 UTC+1 daveford...@gmail.com wrote:

Total ruby noob and first time trying to right a custom fact. It does look too 
complication and I've sort of got this working.. But one question - from the 
puppet documentation gives two ways of using a 'confine'.

This lets me custom fact produce output via facter on my gentoo box as expected
confine :kernel => "Linux"

But this produces no output -
confine :kernel do |value|
value == "Linux"
end
What am I failing to understand- the documentation would suggest both should 
work?
Am trying this on a Mint box running facter 4.4.0 and ruby 3.0.2

Thanks in advance.
Dave

--
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/1da07872-5d29-42e8-9aa6-62c3feb4087fn%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/E2A73317-C756-4853-8E34-9AF19276BCBC%40perforce.com.

[Puppet Users] Vox Pupuli Elections, 2024 (ends May 15)

['Ben Ford' via Puppet Users]

Hello friends!

After a slight delay, we are opening the voting period for this year's PMC 
elections. Votes will be accepted until **May 15 2024 23:59 UTC.**

Please help us select the Vox Pupuli Project Management Committee for the 2024 
year. The people on this committee will help take care of the Code of Conduct 
and its values, participate in strategic planning, and decision making using 
lazy consensus, amongst other things.

New this year, we are also adding two specialized roles:
- The accounting officer will keep track of budget, expenses, and 
sponsorships.
- The social media officer will coordinate social, blog, and other 
similar activities. They're not necessarily responsible for -all- content, but 
will help facilitate it.

These roles will be self selected amongst the committee after the election 
concludes.

Visit the page below to read more about the candidates and to make your choices.

- 
https://civs1.civs.us/cgi-bin/vote.pl?id=E_c3a85d1acd3e9feb=dc65601945c5628c

Thank you so much for your help!


- Ben and the Vox Pupuli PMC.

This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/6789491E-0057-42C1-991E-CA7552C80BB3%40perforce.com.

Re: [Puppet Users] Puppet Server Requirements Documentation Needs Updating

[Ben Ford]

Can you file that as an issue on 
https://github.com/puppetlabs/puppet-docs/issues please?

Thanks!



> On Mar 7, 2024, at 11:25 AM, Nathaniel Black 
>  wrote:
> 
> I think Java requirements documentation needs to be updated. On "Installing 
> Puppet Server" for 7.29.1, it says that Java 8 is still supported.
> https://www.puppet.com/docs/puppet/7/server/install_from_packages
> On an Amazon Linux 2 server with Java 8 (java-1.8.0-openjdk-headless.x86_64 / 
> 1:1.8.0.402.b06-1.amzn2.0.1):
> After I upgraded puppetserver from 7.14 to 7.16 and puppetdb from 7.15 to 
> 7.17, puppetdb kept crashing:
> Requesting shutdown: java.lang.NoSuchMethodError: 
> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer
> It seems that Puppet is recently taking advantage of something not present in 
> Java 8 (some method existed at compile time but is not present for the 
> runtime). Upgrading the server to Java 17 resolved the issue 
> (java-17-amazon-corretto-headless.x86_64)
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/e551008e-6b46-46e9-9f33-5fec16fc5f6cn%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/1032820C-623F-47D0-AB91-44C744F1BE4A%40gmail.com.

[Puppet Users] Vox Pupuli Elections, 2024 edition

['Ben Ford' via Puppet Users]

As announced at CfgMgmtCamp last week, we are kicking off the more-or-less 
annual PMC elections process. This is a yearly process to provide more people 
opportunities to get involved with our leadership and decision making. Would 
you like to help set roadmap or help architect our Puppet 8 support plans? Do 
you want to help organize events or run social media? Do you love spreadsheets 
and want to help with accounting and fundraising? Maybe you’d like to help 
curate our blog or source content from fresh writers.

Maybe you just want to get involved and help out with whatever is needed. 
Joining the PMC is your avenue to this involvement.

Starting today, you may nominate yourself or someone else for the elections. 
Nominations are open until March 22 2024 23:59 UTC and then we’ll vote to 
select the 5 new members of the PMC.

See the elections page in our plumbing 
repository
 for nomination instructions.

I’ll be your elections officer this year. I hope to see your PR soon, and I’ve 
got a Vox hoodie for the first person to submit a nomination.

Thanks!


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/9FDFC9B0-DA70-4DB3-A694-D08F2C8D8D36%40perforce.com.

Re: [Puppet Users] Error 500 on SERVER undefined method safe_load

['Ben Ford' via Puppet Users]

Hey James! That error sounds like you have an out-of-date Psych YAML gem.

What versions of Puppet, Ruby, Hiera, and Psych are you using?



On Nov 8, 2023, at 8:54 AM, James Millsap  wrote:

We have a fairly mature puppet instance along with foreman for classification.  
For some reason, yesterday, everything started failing with this error:

Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: Evaluation Error: Error while evaluating a Function Call, 
undefined method `safe_load' for Puppet::Util::Yaml:Module (file: 
/etc/puppetlabs/code/environments/production/manifests/site.pp, line: 3, 
column: 1) on node hostname.company.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Line 3 of the site.pp is just this:
hiera_include('classes', '')

Which has not changed in many years.  There is either a bug that appeared from 
nowhere, or a syntax error buried somewhere.  I have been going through our 
repository and rolling back every yaml change, but so far nothing has worked.  
If anyone has a clever way to get puppet to give me some more information so I 
can find this, I would be eternally grateful.

--
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/cb051ca4-92a5-43c7-a7d0-9e8942b0af73n%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/7547DCB3-6ACE-46A7-AA63-157FEB0328D1%40perforce.com.

[Puppet Users] Public issue reporting is back!

['Ben Ford' via Puppet Users]

I’m happy to share that public issue reporting is back. You can now file issues 
directly in GitHub right on the project itself using the GitHub account you 
probably already have.

Issue creation is now enabled in the following projects – PA, PUP, PDB, SERVER 
and FACT. We will be reviewing any new issues created using our normal triage 
process and update tickets accordingly. Since planning happens internally you 
may not see much activity on the issue until it’s being actively worked on.

We are working on a process to migrate existing tickets and we will provide an 
update on that soon. Until then you can still view existing tickets on the 
https://puppet.atlassian.net

Thank you for all the input you provide us and we hope that this makes it 
easier to contribute going forward.

-- Puppet Community and Engineering



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/6D73898A-5C57-495D-B6AA-B9268005E58F%40perforce.com.

Re: [Puppet Users] How to create new tickets now?

['Ben Ford' via Puppet Users]

Hi Dirk.

Unfortunately we ran into a few snags in the planned migration of the Jira 
instances. The team is working on evaluating the best ways for resolving them 
and we'll keep you all posted as soon as we have information to share. I can't 
give a firm timeline, but my own personal expectation is that it's resolved in 
the next week or so.

In the meantime, if you've got something important to report, you can write it 
up and share on this mailing list. I'll file it for you and link to the email 
to make sure we get updates back to you.

Apologies for the confusion!



On Aug 25, 2023, at 6:49 AM, 'Dirk Heinrichs' via Puppet Users 
 wrote:

Hi,

PuppetLabs seems to have migrated 
https://tickets.pupptlabs.com to a cloud-based 
Jira instance. As it seems, I can not login to this instance anymore, neither 
with the credentials I used on the old Jira, nor with my Atlassian account. How 
can I  access my tickets now, or even file new ones?

Thanks...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

--
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/dc553744fd35b41b6a8a1c72304397f898bab535.camel%40opentext.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/F2BB6E55-ED1C-4885-9798-88C1274105FF%40perforce.com.

Re: [Puppet Users] How does 'os' facter be determined?

['Ben Ford' via Puppet Users]

Here is an example pull request teaching Facter about the Mariner distro.

https://github.com/puppetlabs/facter/commit/83c51ff227696cfd8e30ed62b6053ede047ca7e4



On May 30, 2023, at 3:47 AM, 羽色云烟  wrote:

facter os on system OpenEuelr shows:
{
  architecture => "aarch64",
  family => "Openeuler",
  hardware => "aarch64",
  name => "openEuler",
  release => {
full => "22.03",
major => "22.03"
  },
  selinux => {
enabled => false
  }
}
This special family cause many modules fail to work. But in fact it can be 
managed the same as Redhat. So we hope to make puppet recogniz this system as 
redhat family, maybe some modification to release file or other tricks to cheat 
puppet.
So, how does puppet facter determine the os name and family?


--
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/ee665705-542b-4afa-b747-7aee31a6b79fn%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/639DF1F0-1C0A-49AF-A24F-C1FD58A009CE%40perforce.com.

Re: [Puppet Users] using vault

['Ben Ford' via Puppet Users]

Deferred functions run on the agent. The Vault connection will be made from the 
agent. Therefor, if you configure Vault using environment variables, you'll 
want to do so from the agent. If you're using systemd, you should be able to 
configure those in the .service file as you suggest.




On May 24, 2023, at 12:13 PM, 'sli...@verizon.net' via Puppet Users 
 wrote:

Hello,

I have vault set up using role and secret id
I downloaded puppetlabs-vault module and saw the code snippet with that module 
https://www.puppet.com/integrations/vault-by-hashicorp

With vault_lookup::lookup deferred method, i don't want to pass my role and 
secret, so other option is set as environment variables. Question is do i need 
to set that up on puppet server or puppet agent? Where may be the best place to 
set that up? if it is on puppet server, can i set that up in say puppet.service 
file? if on agent, where may be the right place to set that up?

Thanks

S

--
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/4792f478-c0a9-4b3c-b51e-eef9bc107f0dn%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/C92B442F-5FA0-4451-B6F7-09436857DF28%40perforce.com.

Re: [Puppet Users] Puppet trial license file.

['Ben Ford' via Puppet Users]

You should not need a license.key for a PE trial. The CD4PE yaml file will let 
you also trial CD4PE.



On Mar 2, 2023, at 7:49 AM, eager2learn  wrote:

I request a trial license for my Puppet Enterprise installation.
I got a CD4PE.yaml file.
But the Puppet Enterprise installation requires a license.key file.
Is it possible to create a license.key file from that CD4PE.yaml file?
If no, how can I get a license.key file with a trial license?
What is the syntax of a license.key file?

--
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/fcca2f21-2e9d-4d37-8009-67ba1d246b70n%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/9DAB30BA-070D-46C4-BE14-D9BCBD8B887A%40perforce.com.

[Puppet Users] Upcoming network maintenance

[Ben Ford]

Hey folks,

This Saturday December 10th starting at 9:00 AM PST, the Puppet IT team is 
going to be performing some network maintenance that will result in our Jira 
instance being intermittently available or unavailable for up to several hours. 
We don't expect the Forge to be affected, but in an abundance of caution, 
suggest scheduling major deployments to avoid this maintenance window.

Further updates will be posted in the #announcements channel of the Puppet 
Community Slack and you can follow along there as work progresses.
 - http://puppetcommunity.slack.com/app_redirect?channel=announcements

We apologize for the late notice, and any inconvenience this may cause you.

Thanks all!

- the Puppet IT team.

This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/86FAA6EF-0303-4B1A-A13A-82433178F07C%40perforce.com.

[Puppet Users] Re: Puppet can't fetch catalog

[Ben Ford]

(and then you'll need to restart the server)

On Tuesday, September 20, 2022 at 7:38:45 AM UTC-7 Ben Ford wrote:

> On the Puppet server, you will need either both of these parameters 
> set (when using Satellite for classification), or both of them unset (when 
> not using Satellite for classification).
>
>
> *external_nodes = /etc/puppetlabs/code/node.rbnode_terminus = exec*
>
>
>
>
> On Thursday, September 15, 2022 at 9:15:51 AM UTC-7 acia...@icloud.com 
> wrote:
>
>> Hello all,
>>
>> my apologies if this topic is already discussed. I try to research it but 
>> I didn't find any solution.
>>
>> I have the following infrastructure:
>>
>> One RHEL Satellite 6 with several capsule server around our datacentres.
>> I implement puppet and ansible correctly, sync the puppet environment 
>> with rsync (the RHEL Sync doesn't work).
>>
>> I moved to RHEL satellite 6.11 (where they remove the puppet support, but 
>> still in the code). I install again puppet on all server.
>> On the principal satellite server works perfectly, but on capsule servers 
>> not.
>>
>> [root@am-sv-satcap02 opt]# puppet agent -t
>> Info: Using environment 'production'
>> Info: Retrieving pluginfacts
>> Info: Retrieving plugin
>> Error: Could not retrieve catalog from remote server: Error 500 on 
>> SERVER: Server Error: Failed when searching for node 
>> am-sv-satcap02.linux.netops.local: You must set the 'external_nodes' 
>> parameter to use the external node terminus
>> Warning: Not using cache on failed catalog
>> Error: Could not retrieve catalog; skipping run
>> [root@am-sv-satcap02 opt]#
>>
>> Some, can help me to sort out of this problem?
>>
>> All the best
>>
>> Alex
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/dce05a05-a9f1-48a1-9d1b-00a146d75e60n%40googlegroups.com.

[Puppet Users] Re: Puppet can't fetch catalog

[Ben Ford]

On the Puppet server, you will need either both of these parameters 
set (when using Satellite for classification), or both of them unset (when 
not using Satellite for classification).


*external_nodes = /etc/puppetlabs/code/node.rbnode_terminus = exec*




On Thursday, September 15, 2022 at 9:15:51 AM UTC-7 acia...@icloud.com 
wrote:

> Hello all,
>
> my apologies if this topic is already discussed. I try to research it but 
> I didn't find any solution.
>
> I have the following infrastructure:
>
> One RHEL Satellite 6 with several capsule server around our datacentres.
> I implement puppet and ansible correctly, sync the puppet environment with 
> rsync (the RHEL Sync doesn't work).
>
> I moved to RHEL satellite 6.11 (where they remove the puppet support, but 
> still in the code). I install again puppet on all server.
> On the principal satellite server works perfectly, but on capsule servers 
> not.
>
> [root@am-sv-satcap02 opt]# puppet agent -t
> Info: Using environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
> Server Error: Failed when searching for node 
> am-sv-satcap02.linux.netops.local: You must set the 'external_nodes' 
> parameter to use the external node terminus
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> [root@am-sv-satcap02 opt]#
>
> Some, can help me to sort out of this problem?
>
> All the best
>
> Alex
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/7ee760a3-e5f3-4b24-b9ad-9dbc099c09dcn%40googlegroups.com.

Re: [Puppet Users] Hiera values in provider

[Ben Ford]

Not directly. Hiera provides data to the server for use when compiling the
catalog. Providers run on the agent after the catalog has been compiled.

If you need to get to Hiera data, write your type/provider such that it
accepts a parameter, then look that up from Hiera and pass it in when you
declare a resource.

On Mon, Aug 1, 2022 at 12:06 PM Matthias K  wrote:

> Hi, is it possible to access hiera values within a custom provider?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/7b664134-0ed6-44d8-8054-b48f8de4e578n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6OfeJ1HU3RRAJt%3DoyCPtiy1Vba%2BLxGZ6uXjoeq9%2BbkFQ%40mail.gmail.com.

[Puppet Users] Re: sensitive password for the active directory module

[Ben Ford]

This page will help you learn how to create a Sensitive string for that 
parameter. https://puppet.com/docs/puppet/latest/lang_data_sensitive.html

On Monday, July 18, 2022 at 11:28:45 AM UTC-7 hanno...@gmail.com wrote:

> hello  puppet users 
>
>  i start installation of puppet with foreman and i need a active directory 
> module .
> cause all active directory modules its with error message like 
> like active directory module in the forge puppet  give a message : 
> senstive password 
>
>
>
>
> Class[Active_directory::Domain_controller]: parameter 
> 'domain_credential_passwd' expects a Sensitive[String] value, got String 
> parameter 'safe_mode_passwd' expects a Sensitive[String] value, got String 
>
>
>
> any solution for this ???
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/264d33d9-b2ac-4a0e-a74e-ab5d12f53210n%40googlegroups.com.

[Puppet Users] Re: training.foreman.com httpd[18624]: SSLCertificateFile: file '/etc/puppetlabs/puppet/ssl/certs/training.foreman.com.pem' does not exist or is empty

[Ben Ford]

Hey there! You'll probably get better help with a Foreman problem on their 
forums. https://community.theforeman.org

Good luck!

On Friday, November 12, 2021 at 10:27:40 AM UTC-8 irtizahs...@gmail.com 
wrote:

> Hi Team,
>
> I tried to run the foreman installer but it throwed lot of errors related 
> to httpd service:
>
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: Starting The Apache HTTP Server...
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com httpd[18624]: AH00526: Syntax error on line 67 of 
> /etc/httpd/conf.d/05-foreman-ssl.conf:
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com httpd[18624]: SSLCertificateFile: file 
> '/etc/puppetlabs/puppet/ssl/certs/training.foreman.com.pem' does not exist 
> or is empty
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: httpd.service: Main process exited, 
> code=exited, status=1/FAILURE
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: httpd.service: Failed with result 
> 'exit-code'.
>
>
> *Could someone please look into this issue & address it.*
>
> Regards,
> Shahid
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: Failed to start The Apache HTTP Server.
> 2021-11-12 05:35:41 [ERROR ] [configure] 
> /Stage[main]/Apache::Service/Service[httpd]/ensure: change from 'stopped' 
> to 'running' failed: Systemd start for httpd failed!
> 2021-11-12 05:35:41 [ERROR ] [configure] journalctl log for httpd:
> 2021-11-12 05:35:41 [ERROR ] [configure] -- Logs begin at Fri 2021-11-12 
> 05:31:02 UTC, end at Fri 2021-11-12 05:35:41 UTC. --
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: Starting The Apache HTTP Server...
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com httpd[18624]: AH00526: Syntax error on line 67 of 
> /etc/httpd/conf.d/05-foreman-ssl.conf:
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com httpd[18624]: SSLCertificateFile: file 
> '/etc/puppetlabs/puppet/ssl/certs/training.foreman.com.pem' does not exist 
> or is empty
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: httpd.service: Main process exited, 
> code=exited, status=1/FAILURE
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: httpd.service: Failed with result 
> 'exit-code'.
> 2021-11-12 05:35:41 [ERROR ] [configure] Nov 12 05:35:41 
> training.foreman.com systemd[1]: Failed to start The Apache HTTP Server.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/e4bd3d0d-8c6d-4337-9a97-72463e6c24b9n%40googlegroups.com.

[Puppet Users] Re: [voxpupuli] Do you have opinions on what module quality means?

[Ben Ford]

I like the idea of an expand button. We'll probably use something like
that. On the other hand, the primary use case of the Forge quality scores
is that of a user trying to evaluate and choose modules, so we're highly
focused on that. We probably won't confuse it too much with specific
details for the author. HOWEVER.

By end-of-year, I'm writing a score preview extension for the new PDK as a
demo of the plugin system so as a module author, you'll get that feedback
during the development phase, even before publishing it. Yay, look at that.
A plugin system so easy that a product manager can use it, and a tool that
gives you early feedback, right when you need it the most!

On Thu, Nov 4, 2021 at 10:14 AM Nick Maludy  wrote:

> Ben,
>
> As you describe the summary scores for new users that makes sense. One UI
> idea i just had as i read your reply was the following:
>
> - Give an overall summary score "4.3" or something
>   - Have a "+" or ">" button that can expand that score and show the
> components that went into it
>   - For each line item show how much each line was worth. This way you can
> total up the score.
>   - Also show the things that were missing and how many points they were
> worth. This way module developers know what needs to be fixed/improved in
> order to raise their score.
>
> Just an idea I had and wanted to "brain dump" while it was fresh.
>
> -Nick
>
> On Thu, Nov 4, 2021 at 12:56 PM Ben Ford  wrote:
>
>> On Thu, Nov 4, 2021 at 8:11 AM Gene Liverman 
>> wrote:
>>
>>> After reading through all the replies, there are bits and pieces from
>>> many people that seem to cover most of my opinions. I am going to try and
>>> collect those here:
>>>
>>> What about this idea? Instead of trying to "measure quality" as a
>>>> metric, maybe try to expose individual checks or metrics about various
>>>> aspects of a module and let the user decide "is this high quality for me,
>>>> or not"?
>>>>
>>> I like this idea. Present a reasonable set of data about things
>>> different users may care about, or might should care about, along with a
>>> link to some docs explaining why people care about the listed things.
>>>
>>
>> This makes it real easy for Puppet experts to read, but doesn't do much
>> for new or casual users. This is why we turned the detail view off
>> temporarily on the Forge. Innocuous warnings were unfairly frightening
>> users away from decent modules without high scores. Our roadmap for the
>> rest of the year includes working on a more user friendly view that will
>> reintroduce the details in a more comprehensible way. Some of the score
>> explanations are being driven by this very conversation!
>>
>>
>> Regarding unit tests, I find the utilization of rspec-puppet-facts
>>> <https://github.com/voxpupuli/rspec-puppet-facts> (and thereby facterdb
>>> <https://github.com/voxpupuli/facterdb>) to be a must. I have this
>>> opinion for two reasons:
>>> 1) as a maintainer, it ensures that my tests work for all the things I
>>> have listed in metadata.json (or at least those supported by the gems)
>>> which is great in general and especially important when the supported OS
>>> lists gets modified.
>>> 2) as a user, if I am looking into how a module works it helps me see
>>> that the maintainer is testing across all the needed OS's quickly and
>>> without having to read every line of every spec test looking for OS combos
>>> that I care about.
>>>
>>
>> This is an interesting point. Maybe I'll expand the scope of this just a
>> bit to ask a more meta question. If we're programatically assigning a
>> quality score, do we think that it's a good idea to give points for
>> adhering to a "standard" testing toolchain? eg, puppetlabs_spec_helper,
>> facterdb, pdk, etc.
>>
>> And if we do, then what about modules in which facterdb doesn't actually
>> provide any benefits? A module that doesn't use facts doesn't need to test
>> with different factsets. How would we distinguish between those cases?
>>
>>
>> As a user, I want to see that there are at least minimal tests covering
>>> public bits - aka at least a "it { is_expected.to compile.with_all_deps
>>> }" run via rspec-puppet-facts on each supported os. I prefer to see more
>>> but also understand that many people who write puppet code are not nearly
>>> as comfortable writing tests.
>>>
>>
>> I'm inclined to say that the bar is that a

[Puppet Users] Re: [voxpupuli] Do you have opinions on what module quality means?

[Ben Ford]

On Thu, Nov 4, 2021 at 8:11 AM Gene Liverman 
wrote:

> After reading through all the replies, there are bits and pieces from many
> people that seem to cover most of my opinions. I am going to try and
> collect those here:
>
> What about this idea? Instead of trying to "measure quality" as a metric,
>> maybe try to expose individual checks or metrics about various aspects of a
>> module and let the user decide "is this high quality for me, or not"?
>>
> I like this idea. Present a reasonable set of data about things different
> users may care about, or might should care about, along with a link to some
> docs explaining why people care about the listed things.
>

This makes it real easy for Puppet experts to read, but doesn't do much for
new or casual users. This is why we turned the detail view off temporarily
on the Forge. Innocuous warnings were unfairly frightening users away from
decent modules without high scores. Our roadmap for the rest of the year
includes working on a more user friendly view that will reintroduce the
details in a more comprehensible way. Some of the score explanations are
being driven by this very conversation!


Regarding unit tests, I find the utilization of rspec-puppet-facts
>  (and thereby facterdb
> ) to be a must. I have this
> opinion for two reasons:
> 1) as a maintainer, it ensures that my tests work for all the things I
> have listed in metadata.json (or at least those supported by the gems)
> which is great in general and especially important when the supported OS
> lists gets modified.
> 2) as a user, if I am looking into how a module works it helps me see that
> the maintainer is testing across all the needed OS's quickly and without
> having to read every line of every spec test looking for OS combos that I
> care about.
>

This is an interesting point. Maybe I'll expand the scope of this just a
bit to ask a more meta question. If we're programatically assigning a
quality score, do we think that it's a good idea to give points for
adhering to a "standard" testing toolchain? eg, puppetlabs_spec_helper,
facterdb, pdk, etc.

And if we do, then what about modules in which facterdb doesn't actually
provide any benefits? A module that doesn't use facts doesn't need to test
with different factsets. How would we distinguish between those cases?


As a user, I want to see that there are at least minimal tests covering
> public bits - aka at least a "it { is_expected.to compile.with_all_deps
> }" run via rspec-puppet-facts on each supported os. I prefer to see more
> but also understand that many people who write puppet code are not nearly
> as comfortable writing tests.
>

I'm inclined to say that the bar is that a spec file exists for each
manifest. (Ewoud's use case of defining the tests in a single loop instead
could be handled by him putting in a file for each path with just a comment
explaining where the test actually lives, or something similar.) It would
be better to use rspec-puppet test coverage, but I don't think we're ready
to actually run the tests on module publication yet. (future improvement?)



> Regarding integration tests, I love to see them but it takes a lot more
> knowledge to write them than it does to write a good puppet module. I would
> love to see straight away that a module has them (and that CI executes
> them) but wouldn't hold it against an author that they don't have any.
>

What if the view included a list of platforms the module has acceptance
tests for. Informational only, rather than affecting the overall quality
score. This would obviously only know the standard testing toolchain(s), of
course, but I think this is doable.


Personally, I find having a module documented with puppet-strings to be
> critical for two reasons:
> 1) it provides lots of useful information within the source code of the
> module
> 2) it enables the programmatic generation of a REFERENCE.md file that can
> then be read on GitHub/GitLab and rendered on the Forge.
>
> Examples can also be contained within this and there by be referenced by
> users in either location too. I think README.md should have a very minimal
> set of examples in it. Most examples should be kept closer to what they are
> describing via puppet-strings IMO.
>
> Speaking of the README.md, I think looking for select key sections would
> be worthwhile. I think it should contain the following at a minimum:
> - an H1 title at the top
> - badges
>   - that show the version released on the Forge and link to the module on
> the Forge
>   - build status
>   - license (ideally via the shields.io badge that reads the license file)
> - an H2 Usage section
> - an H2 Reference section that contains at least text referencing
> REFERENCE.md
> - an H2 Changelog section that at least contains text referring to
> CHANGELOG.md
>

Sounds like a puppet-readme-lint tool to me! We can improve the spec

[Puppet Users] Re: [voxpupuli] Do you have opinions on what module quality means?

[Ben Ford]

:
>
>- Arrow Alignment
>- Indentation
>- Trailing comma (either have or don't have it - standardization is
>good)
>- All the checks included in
>
> https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins/blob/master/voxpupuli-puppet-lint-plugins.gemspec
>
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvoxpupuli%2Fvoxpupuli-puppet-lint-plugins%2Fblob%2Fmaster%2Fvoxpupuli-puppet-lint-plugins.gemspec=04%7C01%7CJohn.Bollinger%40StJude.org%7Ccf737d31ff9549b6860a08d99aea80b7%7C22340fa892264871b677d3b3e377af72%7C0%7C0%7C637711154851057833%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=I%2FSmlN1tMXANeU7XowSyYW%2F9Uq5u11Ej7yoD58NwMtA%3D=0>
>
> For tests use badges for the following:
>
>- Unit tests with rspec-puppet
>- Acceptance/Integration tests with Beaker/Litmus/test-kitchen
>- A README
>- A generated REFERENCE.md from puppet-strings
>- Changelog that can be embedded into the Forge page
>
> Things that I find too subjective to use a markers for quality:
>
>- Use only vendor/OS provided packages:
>While I can see why some would want this, I personally have not worked
>at a place that could utilize OS provided packages for a lot of non-OS
>level software. Things like Nginx, Ruby, Go, Apache, PHP, etc tend to be
>too old even in Ubuntu to use for running applications and in most cases
>the OS packages/repos have turned into just what is needed to support
>running applications that contain or install their own requirements -
>either via containerization or vendor/project provided repositories.
>- Don't include binaries:
>This one is, for me, a hard no. With Modules that include Bolt tasks,
>you limit what kinds of tasks can be included or what languages those tasks
>can be written in which could be limiting as there are a lot in the Puppet
>community not interested in learning Ruby, but want their tasks to do work
>that can't necessarily be done by bash or powershell scripts. So allowing
>those users to built tasks in Go, Rust, etc is a no brainer, IMO.
>
>
>
> Thoughts?
>
> ---
>
> David Hollinger III
>
> Software Engineer
>
> WPEngine
>
>
>
> Sent with ProtonMail
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotonmail.com%2F=04%7C01%7CJohn.Bollinger%40StJude.org%7Ccf737d31ff9549b6860a08d99aea80b7%7C22340fa892264871b677d3b3e377af72%7C0%7C0%7C637711154851057833%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=KWlq3y32NYPtUbV3ki7Xnva7TeIzylTqUMu%2BfCpsXE4%3D=0>
> Secure Email.
>
>
>
> ‐‐‐ Original Message ‐‐‐
> On Thursday, October 28th, 2021 at 3:33 PM, Ben Ford 
> wrote:
>
> Trick question, I know. Having strong opinions is part of why we do the
> work we do. So I'm hoping that many of you will help us out on this
> project.
>
>
>
> Some time ago, the Forge turned off the quality scores detail display
> because many of the warnings were confusing and frightening to less
> experienced Puppet users. And we didn't really have a good specification of
> what made quality code anyway. That's what I hope to improve on today, and
> we'd like to turn it back on with a better picture of each module's quality.
>
>
>
> Vox Pupuli has a meta-gem that defines a list of the puppet-lint checks
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvoxpupuli%2Fvoxpupuli-puppet-lint-plugins%2Fblob%2Fmaster%2Fvoxpupuli-puppet-lint-plugins.gemspec=04%7C01%7CJohn.Bollinger%40StJude.org%7Ccf737d31ff9549b6860a08d99aea80b7%7C22340fa892264871b677d3b3e377af72%7C0%7C0%7C637711154851067794%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=Y%2FlqbI0AptAG66MGn1MITMXJMJzISp7aYiTyBoKohXA%3D=0>
> that they use for their definition of a quality Puppet module. I'd like the
> Forge and Vox Pupuli to be in alignment here, and this seems like the best
> place to start.
>
>
>
> Do you have a favorite list of puppet-lint checks you use? Do you think
> they'd be useful as an ecosystem standard? Can you support that opinion
> with a cogent argument for it? Suggest it as a pull request and let's have
> that conversation. Together as a community we can all come up with a solid
> starting point as a standard definition of module quality.
>
>
>
>
> https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins/blob/master/voxpupuli-puppet-lint-plugins.gemspec
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvoxpupuli%2Fvoxpupuli-puppet-lint-plugins%2Fblob%2Fmaster%2Fvoxpupuli-puppet-lint-

[Puppet Users] Do you have opinions on what module quality means?

[Ben Ford]

Trick question, I know. Having strong opinions is part of why we do the
work we do. So I'm hoping that many of you will help us out on this project.

Some time ago, the Forge turned off the quality scores detail display
because many of the warnings were confusing and frightening to less
experienced Puppet users. And we didn't really have a good specification of
what made quality code anyway. That's what I hope to improve on today, and
we'd like to turn it back on with a better picture of each module's quality.

Vox Pupuli has a meta-gem that defines a list of the puppet-lint checks
<https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins/blob/master/voxpupuli-puppet-lint-plugins.gemspec>
that they use for their definition of a quality Puppet module. I'd like the
Forge and Vox Pupuli to be in alignment here, and this seems like the best
place to start.

Do you have a favorite list of puppet-lint checks you use? Do you think
they'd be useful as an ecosystem standard? Can you support that opinion
with a cogent argument for it? Suggest it as a pull request and let's have
that conversation. Together as a community we can all come up with a solid
starting point as a standard definition of module quality.

https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins/blob/master/voxpupuli-puppet-lint-plugins.gemspec

Thank you all for your help!

-- 
Ben Ford
@binford2k
Ecosystem Product Manager

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4gcxn%3Dd-R0PLEhtV9n0YqJ-ry%3DnWJzweCsBAeQ2%3DCYLQ%40mail.gmail.com.

Re: [Puppet Users] Getting the location of the manifest file

[Ben Ford]

Hiera provides an environment hierarchy. Is that what you're looking for?
https://puppet.com/docs/puppet/latest/hiera_config_yaml_5.html

On Mon, Aug 16, 2021 at 7:33 PM Go Iwai  wrote:

> Hello Martin,
>
> Let's say we have three directories:
>
> preproduction/  preproduction/  private/
>
> There are different manifest files saved in the same name, like
> service-deploy.pp.
>
> In the manifest service-deploy.pp, I want to get the absolute path to
> itself, then determine the variable of env like:
>
> $dir = dirname($file)  # $file is absolute path to service-deploy.pp
> like: '/path/to/manifests/preproduction/service-deploy.pp'
> $env = split($dir, '/')[-1]
>
> Then, hiera dynamically maps the correspond yaml file under the $env like:
>
> mapped_paths: [services, svc, "environments/%{env}/%{svc}.yaml"]
>
> This is what I want to realise. I know puppet has already provided a
> switch in response to $environment, e.g.,
> /etc/puppetlabs/code/environments/production. In this way, I have to
> maintain some branches in parallel. That is what I don't want to do.
>
> Kind regards,
> Go
>
> On Mon, Aug 16, 2021 at 7:53 PM Martin Alfke  wrote:
> >
> > Hi Go,
> >
> > what do you want to achieve?
> > When using puppet apply, a manifest can be anywhere on the filesystem.
> >
> > Best,
> > Martin
> >
> >
> > > On 16. Aug 2021, at 03:18, Go Iwai  wrote:
> > >
> > > Hello,
> > >
> > > I want to know the location where puppet-apply locally applied the
> > > manifest file.
> > >
> > > $ pwd
> > > /path/to/manifests
> > > $ puppet apply file.pp
> > >
> > > In this case above, can I anyhow get the location of
> > > /path/to/manifests/file.pp within file.pp?
> > >
> > > Kind regards,
> > > Go
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> > > To unsubscribe from this group and stop receiving emails 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/CAAyfkv-2dC--QR_1tz1ux%2BrgYaVsqjseB4oTEZ-EnkZPNXnn1w%40mail.gmail.com
> .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> > To unsubscribe from this group and stop receiving emails 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/2E04526A-7F74-4F84-99E4-4C1D675FC67C%40gmail.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/CAAyfkv_qCcfWG5tcqkD%2BTAaSRPhr%3DsfCYYUP3q1MXToULxXyJw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L7XSALCjA67chyTjD%2Bpsx0-72kOOf%3D5HTC1kBjdGd3H%2BA%40mail.gmail.com.

Re: [Puppet Users] Getting the location of the manifest file

[Ben Ford]

Hi Go!

I'm not sure what you're trying to accomplish, but you'd probably be better
off locating your code in a module on your modulepath and then Puppet takes
care of all the relative paths for you.
https://puppet.com/docs/puppet/latest/modules_fundamentals.html

On Mon, Aug 16, 2021 at 3:53 AM Martin Alfke  wrote:

> Hi Go,
>
> what do you want to achieve?
> When using puppet apply, a manifest can be anywhere on the filesystem.
>
> Best,
> Martin
>
>
> > On 16. Aug 2021, at 03:18, Go Iwai  wrote:
> >
> > Hello,
> >
> > I want to know the location where puppet-apply locally applied the
> > manifest file.
> >
> > $ pwd
> > /path/to/manifests
> > $ puppet apply file.pp
> >
> > In this case above, can I anyhow get the location of
> > /path/to/manifests/file.pp within file.pp?
> >
> > Kind regards,
> > Go
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> > To unsubscribe from this group and stop receiving emails 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/CAAyfkv-2dC--QR_1tz1ux%2BrgYaVsqjseB4oTEZ-EnkZPNXnn1w%40mail.gmail.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/2E04526A-7F74-4F84-99E4-4C1D675FC67C%40gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4J5pCQeshZO1Nf3sRwdnKoGxy%2BgPUC6Cx66rXdArQUcQ%40mail.gmail.com.

[Puppet Users] Re: Can we have PuppetDB docker images with 6.x latest?

[Ben Ford]

Hi!

We've actually decided to ship only the most current builds (7.x right now) 
across the board to reduce the number of pulls used across the company.

On Thursday, July 15, 2021 at 5:23:36 AM UTC-7 rcm...@gmail.com wrote:

> Just noticed the same behavior with Puppet Server docker images that the 
> latest is now only for version 7.
>
> Maybe we could improve to the same strategy to push 6.x tags as well.
>
> https://github.com/puppetlabs/puppetserver/blob/6.x/.github/workflows/docker.yml
>
> The latest from version 6 on the docker hub is now on 6.14.1.
> https://hub.docker.com/r/puppet/puppetserver/tags
>
> Thanks for the help.
> Cheers!
>
> On Wednesday, July 14, 2021 at 7:58:52 PM UTC-4 Rodrigo Moutinho wrote:
>
>> Hi,
>>
>> Just noticed that once it was changed to "main" branch, we stopped to 
>> push docker images for 6.x. Now only latest 7.x are pushed to dockerhub.
>>
>> https://hub.docker.com/r/puppet/puppetdb/tags
>>
>> Can we add version 6.x to the docker github workflow? (currently the 
>> default branch on GitHub)
>>
>> https://puppet.com/docs/puppetdb/6/release_notes.html
>>
>> https://github.com/puppetlabs/puppetdb/blob/6.x/.github/workflows/docker.yml
>>
>> Seems that the latest docker image for version 6 is 6.13.1 but the latest 
>> is already on 6.18 according to the github tags (
>> https://github.com/puppetlabs/puppetdb/releases/tag/6.18.0). This way we 
>> could continue to have both latest builds for versions 6 and 7.
>>
>> Thanks for the help in advance!
>> Cheers!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/5957cce9-8e42-47fd-9808-1ef3e45600ebn%40googlegroups.com.

[Puppet Users] Razor project archival

[Ben Ford]

Razor was a highly configurable bare-metal provisioning system. It would
let you provision fresh systems via arbitrary rules and let you do things
like PXE boot a whole lab and let it build out all the different kinds of
machines you'd need.

We shipped Razor with Puppet Enterprise starting with version 3.2. But over
the years, we came to realize that it didn't align well with our business
strategy and made the difficult decision to retire it as of Puppet
Enterprise 2019.8, which is our current LTS release.

Now we are finishing that end-of-life process by archiving the following
Razor repositories.

   - https://github.com/puppetlabs/razor-server
   - https://github.com/puppetlabs/puppetlabs-razor
   - https://github.com/puppetlabs/razor-el-mk
   - https://github.com/puppetlabs/pe-razor-vagrant-stack
   - https://github.com/puppetlabs/razor-client
   - https://github.com/puppetlabs/razor-vanagon

In true Open Source fashion, the source code is always available. We'd love
it if a Razor superfan forked these repositories and took the project to
new heights. If that's you, just drop us a line at
open-source-stewa...@puppet.com and we'll help you get started.

So long, old friend!

--
Ben Ford
@binford2k
Ecosystem Product Manager

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4ewptmxYtnFF8krc5zqxRwjpTWxn48Th6y-XxqCwT7Mw%40mail.gmail.com.

Re: [Puppet Users] [INFO, maybe ACTION] r10k Feature Proposal

[Ben Ford]

Hey Molly,

The PDK has already been ignoring the /spec directory for quite some time,
so I think this is totally appropriate. It won't even have any effect for
PDK enabled modules from the Forge. Those files are only used for
development purposes, and if you're doing that in your production codebase,
you should go slap yourself on the wrist! 

Honestly, I'm not even sure that r10k should offer an option to opt out. If
you want the specs to do dev work on the module, then you really ought to
just be cloning it into a workspace in the first place. Working directly in
a deployed control repo is a real good way to get yourself stuck. If you
make changes to files, accidentally or not, you can easily get yourself
into the state where r10k or Code Manager can't even deploy cleanly and
you'll have to either clean up the repo, or nuke it and redeploy. We've
recommended for ages that people just treat the deployed control repo as a
black box.

Cheers!

On Thu, Mar 11, 2021 at 4:07 PM  wrote:

> Molly,
>
>
>
> Should this be an all or nothing or off by default with the option to
> include them?
>
>
>
> Thanks,
>
> Steve
>
>
>
>
>
>
>
>
>
> *From:* puppet-users@googlegroups.com  *On
> Behalf Of *Molly Waggett
> *Sent:* Thursday, March 11, 2021 7:04 PM
> *To:* puppet-users@googlegroups.com
> *Cc:* Froyo Team 
> *Subject:* [Puppet Users] [INFO, maybe ACTION] r10k Feature Proposal
>
>
>
> Hey folks!
>
>
>
> We are planning an r10k feature to stop deploying module spec
> directories. This will lower disk usage, particularly for folks with a lot
> of modules and multiple compilers.
>
>
>
> Our hope is to enable this behavior by default, but leave the option to
> opt out (i.e. continue including spec directories when deploying
> modules). This is based on the assumption that most folks have no need for
> module spec directories in a production environment, since they typically
> just include testing materials for module development.
>
>
>
> If you think this assumption is inaccurate, or even if it’s just
> inaccurate for you, please let us know! If we don’t hear any objections by 
> *Tuesday,
> March 23*, we will proceed with the above plan to adopt this behavior but
> include a way to opt out.
>
>
>
> If you have any questions, please reply to this email or ping @r10k in the 
> Puppet
> Community Slack .
>
>
>
> Thanks!
>
>
>
> --
>
> *Molly Waggett*
>
> she/her
>
> Senior Software Engineer @ Puppet
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/CAFOE68C%2BWNLmtfgJgCUkRkjX-rYqoAUAQvUApa-xp1_k7sp7vA%40mail.gmail.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/155101d716d3%24aa8c9750%24ffa5c5f0%24%40gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4cU8qUc5F%2BLPocg0oKogi9ce3C3vw98azGdHGwAqCg2g%40mail.gmail.com.

Re: [Puppet Users] init config once

[Ben Ford]

I do have a kind of terrible module that does exactly this I make no
guarantees whatsoever about how well it works. I ended up not using it for
much longer after building it.

https://forge.puppet.com/modules/binford2k/manageonce

On Fri, Jan 29, 2021 at 12:14 AM Martin Alfke  wrote:

> A custom fact is the best way to report the status of the file on the node
> to the master and have the file managed by Puppet based on the fact value.
>
> Bolt needs ssh access to the systems (unless you are using Puppet
> Enterprise which does not need ssh but uses a message queue on the master
> and the pxp-agent on the nodes.).
>
> Besides this: Bolt must be executed manually
>
> On 29. Jan 2021, at 06:03, Benjamin Ridley  wrote:
>
> You might be better off using something like Puppet Bolt to deploy the
> file as a one off task at provisioning, rather than trying to manage it
> declaratively through Puppet.
>
> On Fri, 29 Jan 2021, 3:50 pm Steve McKuhr,  wrote:
>
>> In an effort to avoid errors triggered by validate_cmd, I ended up using
>> a conditional based on a File.exists custom fact. I'm still open to
>> suggestions, this is all new territory to me.
>>
>>
>> On Thu, 2021-01-28 at 17:13 -0800, Steve McKuhr wrote:
>> > I've just realized that my problem statement was slightly misleading. A
>> > 'users' file gets installed as part of the software package, and the
>> > goal is replacing its contents during the first Puppet run. The next
>> > Puppet runs should ignore any changes.
>> >
>> >
>> > On Thu, 2021-01-28 at 20:07 +0100, Martin Alfke wrote:
>> > > and please use ensure => file !
>> > > this is more clear.
>> > > you can set the file ensure attribute to one of the following: file,
>> directory, link, absent
>> > >
>> > >
>> > > > On 28. Jan 2021, at 18:58, Ben Ford  wrote:
>> > > >
>> > > > Yep, just use the replace attribute on the file resource.
>> https://puppet.com/docs/puppet/latest/types/file.html#file-attribute-replace
>> > > >
>> > > > On Thu, Jan 28, 2021 at 9:57 AM Steve McKuhr <
>> steve.mck...@gmail.com> wrote:
>> > > > I'd like to initialize a user config file once, at software install
>> time, then allow application admins to manage the file contents via web
>> interface (add/remove users, etc.) - I have come up with the following:
>> > > >
>> > > > file { 'users':
>> > > >   ensure => present,
>> > > >   content => template('my-template'),
>> > > >   validate_cmd => '/bin/test ! -f users.control',
>> > > > }
>> > > > file { 'users.control':
>> > > >   ensure => present,
>> > > >   content => "puppet managed",
>> > > >   require => File['users'],
>> > > > }
>> > > >
>> > > > The above code works ok, however I was wondering if there is a more
>> elegant solution.
>> > > >
>> > > > Thanks,
>> > > > Steve
>> > > >
>> > > >
>> > > > --
>> > > > You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> > > > To unsubscribe from this group and stop receiving emails 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/fb1ae2b4-f220-4d18-864b-aafbadb44b14n%40googlegroups.com
>> .
>> > > >
>> > > > --
>> > > > You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> > > > To unsubscribe from this group and stop receiving emails 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/CACkW_L5oTmsHiwvmVEisKap7gkUt1P4Gmvh1-%3DBQqNtHHiWAcA%40mail.gmail.com
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails 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/7a518ea8c6214ea01e1ce3d6e76273ddfd576493.camel%40gmail.com
>> .
>>
>
> --
> You re

Re: [Puppet Users] init config once

[Ben Ford]

Yep, just use the replace attribute on the file resource.
https://puppet.com/docs/puppet/latest/types/file.html#file-attribute-replace

On Thu, Jan 28, 2021 at 9:57 AM Steve McKuhr  wrote:

> I'd like to initialize a user config file once, at software install time,
> then allow application admins to manage the file contents via web interface
> (add/remove users, etc.) - I have come up with the following:
>
> file { 'users':
>   ensure => present,
>   content => template('my-template'),
>   validate_cmd => '/bin/test ! -f users.control',
> }
> file { 'users.control':
>   ensure => present,
>   content => "puppet managed",
>   require => File['users'],
> }
>
> The above code works ok, however I was wondering if there is a more
> elegant solution.
>
> Thanks,
> Steve
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/fb1ae2b4-f220-4d18-864b-aafbadb44b14n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5oTmsHiwvmVEisKap7gkUt1P4Gmvh1-%3DBQqNtHHiWAcA%40mail.gmail.com.

Re: [Puppet Users] Installing an exe like VLC

[Ben Ford]

Welcome!

I'd actually install Chocolatey and use the provider from
https://forge.puppet.com/modules/puppetlabs/chocolatey to manage packages
like this on Windows.

On Tue, Nov 10, 2020 at 3:31 PM Jarod Schoen 
wrote:

> Hi
> so I just got started and I'm glad to be joining you.
>
> I have a question to get me started on my journey.
>
> Without escalating I get:
> Error: Could not update: The requested operation requires elevation. -
> CreateProcess
>
> So it looks like I have to run puppet with LocalService or some admin
> account. That's fine. I'll have to sort that out later.
>
> The major issue is with running exes.
>
> Here's my pp:
>
> package { 'vlc':
>   ensure  => '3.0.1',
>   source  => 'somepath\vlc-3.0.1-win64.exe',
> #  install_options => ['INSTALLDIR=C:\blabla'],
> }
>
> When I run the Start Command Prompt as admin, it runs... but then VLC asks
> me for input which completely defeats the purpose of puppet in the
> environment.
>
>
> Do you guys know how to get puppet to take care of these installs or would
> I have to find an msi for everything... that already has built-in 'silent'
> and other install config switches ?
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/fb546cff-2acf-4810-8fdf-58c39ef7ce67n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4NT%3D2CPN85gjD18Kmj8H3KS_Njq18GP3-9Hs2EJRmXpg%40mail.gmail.com.

Re: [Puppet Users] External object

[Ben Ford]

On Mon, Nov 9, 2020 at 9:18 AM Albert Shih  wrote:
[...]

> I've check static yaml file, but that's not very convenient, the file can
> be very big (we got ~2000 object cannot run puppet), and because lot of
> host need those informations, I need almost to load them in all node.


Does this mean that each device you're managing is completely unique?
Generally the strength of Hiera is that you can create one or more common
"base layers" of configuration and then define exceptions or overlays based
on criteria that could be "what building the device is in" all the way to
individual device settings.

Have you read much about Hiera hierarchies?
https://puppet.com/docs/puppet/latest/hiera_quick.html

-Ben

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4JxwjZY6NvDHVKoyYstwqdcQhJarL3UOh2ERK1Ca8uXg%40mail.gmail.com.

Re: [Puppet Users] need help for slack join

[Ben Ford]

You’ll find the link on https://puppet.com/community/

Sent from my iPhone

> On Aug 22, 2020, at 4:10 PM, Tej Singh Rana  wrote:
> 
> 
> Hello, Team
>I am not getting links to join slack channel. Puppet has a slack channel 
> like others? Can I get invited URLs to join slack channel?
> 
> thanks,
> -- 
> -
> Tej Singh Rana
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/CADBoQTobZe47TCOu%3D0RJJXyWF2PJOytTV8gXCuGaczM0j4ZxbA%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/6AF28AC9-296A-4729-BEB4-1846031620B5%40puppet.com.

Re: [Puppet Users] updating concat breaks puppet run

[Ben Ford]

Subscribe to Concat['/etc/exports'] instead.

The concat type used to be a defined type that wrapped a file resource many
years ago. It's now a first class citizen itself.

On Thu, Aug 20, 2020 at 4:28 AM Andy Hall  wrote:

> we have updated the concat module and it no longer likes our code...so
> this used to work fine...
>
>   concat { "/etc/exports":
> ensure => present,
>   }
>
>   Concat::Fragment {
> content => "# HEADER: This file is managed by Puppet. DO NOT EDIT.\n",
> order   => '0',
>   }
>
>   concat::fragment { 'nfs_exports_header':
> target  => "/etc/exports",
>   }
>
>   exec { 'reload_nfs_exports':
> command => "exportfs -ra",
> subscribe => File["/etc/exports"],
> refreshonly => true,
>   }
>
> ...but after updating to concat version 6.2 we get this error...
>
> Server Error: Could not find resource 'File[/etc/exports]' in
> parameter 'subscribe' (file:
>
> /etc/puppetlabs/code/environments/production/modules/flex/manifests/profiles/archive/server.pp,
> line: 34)
>
> what has changed for this to break ? does concat itself not declare
> the file ? this works fine once we roll back the version.
>
> any help most appreciated thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/CAOp5WB7Ew4cz%3D1zo8oSHK4Y74kAdqteXWp%3DG%3D1YBZD3Vrx5Sxw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5mmEpXq1o0B4mhxyJ_5zAMHnmx_20swbDb7fswm0%3DMFQ%40mail.gmail.com.

Re: [Puppet Users] Upgrade from puppet 5 to puppet 6

[Ben Ford]

That sounds like the server isn't compiling the code that you think it is.
Can you first restart puppetserver to ensure that it's not just cached, and
then check that you're deploying code correctly and that you're using the
right environment, etc.

Also, try commenting out the resource causing the problem and just ensure
that you're even looking at the right code!



On Wed, Jun 24, 2020 at 9:31 AM Aditya Gupta  wrote:

> Same error is coming even erb file is empty.
>
> On Friday, June 19, 2020 at 1:45:24 AM UTC+5:30, Justin Stoller wrote:
>>
>> providing the erb template would be valuable, if possible.
>>
>> The error looks like someone defined new constants w/in a custom function
>> file.
>> Is your erb file calling a custom function?
>>
>> On Thu, Jun 18, 2020 at 8:08 AM Aditya Gupta  wrote:
>>
>>> Hello All,
>>>
>>> Recently i have updated from puppet-5 to puppet-6 but after upgrade my
>>> erb stop working.
>>> It is throwing error:
>>>
>>> Error: Error while evaluating a Function Call, undefined method `[]' for
>>> Puppet::Pops::Loader::RubyLegacyFunctionInstantiator::Puppet:Module
>>>
>>> Simple resource:
>>> file { '/etc/libvirt/libvirtd.conf':
>>> ensure  => file,
>>> path=> '/etc/libvirt/libvirtd.conf',
>>> content => template('kvm/libvirtd.conf.erb'),
>>> }
>>>
>>>
>>> Please suggest.
>>>
>>> Thanks,
>>> Aditya
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to puppet...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/d541414b-9f12-4d0b-8abf-ecd00f67747ao%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/228686bf-5111-4b99-aa84-84fc3758c00bo%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L74GGuUJYb4QSAw86F8xWW3yoM1R09%3DenVNe82X7VfOJA%40mail.gmail.com.

Re: [Puppet Users] Debugging puppet error : Could not find dependency

[Ben Ford]

Hi Milind,

The critical difference here is that subscribe =>
File[$old_launch_agent_path] does NOT tell Puppet to watch for changes in
that file on disk.

Instead it will run that exec if Puppet itself is managing that resource
and makes changes to that resource. In other words,
File[$old_launch_agent_path] has to be in the catalog, and it only fires
when it's out of sync and Puppet makes changes to it. Something like the
following:

$old_launch_agent_path =
"${home}/Library/LaunchAgents/com.company.program.plist"

file { $old_launch_agent_path:  <--┐
ensure => file,|
#...   |
}  |
   |
 exec { 'stop-old-program':|
command => "/bin/launchctl unload ${old_launch_agent_path}",   |
refreshonly => true,   |
subscribe => File[$old_launch_agent_path], #   ┘
}


On Thu, May 21, 2020 at 10:06 AM Milind Vaidya  wrote:

> *Background*
>
> Puppet Newbie, trying to maintain some old puppet version on a box. The
> aim is to unload an old program using it's old plist file and start new
> one.
>
> *Problem*
>
> I have following code in .pp file
>
> $old_launch_agent_path =
> "${home}/Library/LaunchAgents/com.company.program.plist"
>
> exec {
>   'stop-old-program':
>   command => "/bin/launchctl unload ${old_launch_agent_path}",
>   refreshonly => true,
>   subscribe => [ File[$old_launch_agent_path] ];
> }
>
> *Error: Could not find dependency
> File[/Users/executer/Library/LaunchAgents/com.company.program.plist] for
> Exec[stop-old-program] at
> /private/tmp/mobile-puppet-manifests/puppet-manifests-test/modules/program/manifests/init.pp:51*
>
>
> The changes are on a git branch and are being applied *`sudo puppet-apply
> -d -f -b mac-upgrade`*
>
>
> ls -l /Users/executer/Library/LaunchAgents/com.company.program.plist`
> -rw-r--r--  1 executer  staff  999 May 19 14:36
> /Users/executer/Library/LaunchAgents/com.company.program.plist
>
>
>
> Stack overflow link :
>
> https://stackoverflow.com/questions/61938607/debugging-puppet-error-could-not-find-dependency
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/c580925f-709a-4539-9b8e-c588fb970721%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6VX4-pth0G0eGb60DJtZUPhd_1iOwx%3DexzuXNOdVr6VQ%40mail.gmail.com.

Re: [Puppet Users] Re: Facter 4 release

[Ben Ford]

Since it was developed in parallel, they used
https://github.com/puppetlabs/facter-ng. I don't know if there are plans to
reconcile them in the future, but Bogdan could tell you about that later.

On Mon, Mar 30, 2020 at 2:38 PM Stefan Wrobel  wrote:

> Where is the source for the 4.x releases?
> https://github.com/puppetlabs/facter only seems to have 3.x as the
> latest...
>
> On Wednesday, March 18, 2020 at 9:54:40 AM UTC-7, Bogdan Irimie wrote:
>>
>> Hi,
>>
>> I am very happy to announce the first release of Facter 4
>> . The team has worked
>> tirelessly these last couple of weeks to make the transition for projects
>> that use Facter as a gem (for example Modules CI pipelines) as smooth as
>> possible.
>>
>> If you experience any issues with Facter 4 or you are not ready to
>> migrate to it, you can revert back to Facter 2 by setting Facter version in
>> your gemfile. If you are using rspec_puppet for tests, you can use
>> FACTER_GEM_VERSION to set the Facter version.
>>
>> One of the objectives for Facter 4 is to be compatible with Facter 3, so
>> expect frequent releases that will close the gap between Facter 3 and
>> Facter 4.
>>
>> The entire team is really excited about this release and we are looking
>> forward to your feedback. Feel free to reach out on slack
>>  or open a ticket
>> on https://tickets.puppetlabs.com/projects/FACT with facter-ng label.
>>
>> Best regards,
>> Bogdan Irimie
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/3eb02bc9-2535-4f13-9d2b-8bbeec13fca8%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6CZ6t4%2B-cS4VeA8tevJoHU1hnJUCW_m5rPjFDEUAz2xQ%40mail.gmail.com.

Re: [Puppet Users] Conditional with find_file

[Ben Ford]

On Tue, Jan 21, 2020 at 11:54 AM Gabriel Filion  wrote:

> On 2020-01-20 2:34 a.m., Joaquin Veira wrote:
> > I understand what you mean but I guess there must be any way to check if
> I
> > file exists on the client and act in consecuence.
> >
> > I mean, if I want to identify a MySQL server by the existance of
> > /etc/my.cnf and execute a systemctl enable mysql && systemctl start
> mysql
> > that should work, right?
>
> I guess you could write a boolean custom fact that is true if the file
> exists and false otherwise.
>
> but I guess what Ben was trying to expose was that this makes the logic
> somewhat reversed for what ppl usually do with puppet.
>
> with puppet you usually want to dictate what a machine should have, e.g.
> your logic would read somewhat like "This host is a mysql server".
>
> If you have some manifest that configures something if a certain file
> exists it means that puppet is not authoritative about what a server is
> but is merely reacting to what sysadmins do directly on the machine. It
> also means that if someone installs mysql by mistake or somehow gets an
> /etc/my.cnf file created, then your manifests might wrongly install some
> things as though this machine was supposed to be a production mysql
> server, but without a clear decision about this in your infrastructure
> code.
>


Exactly. Instead of saying "if this is a mysql server, then start mysql"
you are authoritative and say with confidence "This is a mysql server".

This means that Puppet should
  1) install the packages
  2) write configuration files
  3) enable the service

And the benefit of that is you have _all of those_ or you have _none of
those_. Aka, a consistent state that you can trust.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4t8z8xE%2BiBBv2qd1QcZp5ELQ%3DX0Dw%3Djp-YuGuu_7ik1Q%40mail.gmail.com.

Re: [Puppet Users] Conditional with find_file

[Ben Ford]

>
> But when I execute this from a server-client infrastructure it seems like
> the conditionals don't work They are not even processed:


Oh, they're processed just the same. But the key part that you've missed is
that the catalog is compiled on the *master*. That's where all functions
run. The catalog that the agents get is just a json file that describes
what state the system should be in. The reason it appeared to work when you
ran puppet apply was that apply operates like both master and agent in that
it compiles the catalog and then enforces it.

What's the use case you're trying to solve? Writing code that does
different things based on some arbitrary condition that might have
completely different results at different times is generally a brittle
anti-pattern. We generally want a catalog to manage a system with a known
end state.

On Fri, Jan 17, 2020 at 8:15 AM Joaquin Veira 
wrote:

> Hi,
>
> I'm trying to use a condition based on the existance of a file. Something
> like this:
>
> if find_file('/etc/if_this_file_exists') {
> file { '/etc/create_this_file':
> ensure => present,
> owner  => 'root',
> group  => 'root',
> mode   => '0755',
> source =>
> "puppet:///modules/${module_name}/etc/create_this_file",
> }
> }
>
> This is working correctly in a laboratory environment launched with:
>
> [root@labserver ~]# puppet apply --modulepath=/home/user/git/ -e "include
> my_module" --verbose --noop
> Info: Loading facts
> Notice: Compiled catalog for labserver in environment lab in 0.04 seconds
> Info: Applying configuration version '1579255663'
> Notice: /Stage[main]/my_module::Files/File[/...]/mode: current_value
> '0777', should be '0755' (noop)
> Notice: /Stage[main]/my_module::Files/File[/]/mode: current_value
> '0777', should be '0755' (noop)
> Notice: /Stage[main]/my_module::Files/File[/...]/mode: current_value
> '0777', should be '0644' (noop)
> Notice: /Stage[main]/my_module::Files/File[/...]/mode: current_value
> '0777', should be '0770' (noop)
> Notice: /Stage[main]/my_module::Files/File[/...]/ensure: current_value
> 'absent', should be 'file' (noop)
> Notice: Class[my_module::Files]: Would have triggered 'refresh' from 5
> events
> Notice: Stage[main]: Would have triggered 'refresh' from 1 event
> Notice: Applied catalog in 0.12 second
>
> But when I execute this from a server-client infrastructure it seems like
> the conditionals don't work They are not even processed:
>
> [root@devserver ~]# puppet agent -tv --debug --noop
> ...
> Debug: /Stage[main]/previous_module::Install/File[/...]: Adding
> autorequire relationship with User[root]
> Debug: /Stage[main]/my_module::Files/File[/...]: Adding autorequire
> relationship with File[/etc/cron.daily]
> Debug: /Stage[main]/my_module::Files/File[/...]: Adding autorequire
> relationship with User[root]
> Debug: /Stage[main]/next_module::Config/App::Conf[00-syslog]/File[/...]:
> Adding autorequire relationship with User[root]
> ...
>
> Sorry I have to modify the output so I don't show the real paths & files.
>
> Can anyone explain to me why is this not working, please?
>
> Thanks & regards,
>
> Joaquín
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/a13df78f-e816-47e8-92d7-3cc46c316276%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6d2NR-qpR1hg15ufWSNSrJZfBconn1WCt4N4bSUk_wKQ%40mail.gmail.com.

Re: [Puppet Users] Could not find resource 'File[/etc/logrotate.d/syslog]

[Ben Ford]

Hi Dan!

When you subscribe to another resource like subscribe =>
File['/etc/logrotate.d/syslog'], the key is that you're not actually
subscribing to the file on disk. You're subscribing to *another Puppet
resource*, of type File and with a title of '/etc/logrotate.d/syslog'. Any
time that Puppet makes changes to the resource, that notification will
trigger.

Here's a graphic that shows how the relationship works. References in the
Puppet code point to resource declarations in Puppet code, not to the
artifacts on the system that are managed by those resource declarations.

[image: reference_manifest.png]

This means that unless you're actually managing that file with Puppet code,
the relationship won't work.


On Tue, Oct 22, 2019 at 2:27 PM Dan Crisp  wrote:

> Hi,
>
> I'm seeing the following error when running the agent on a server:
>
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
> Server Error: Could not find resource 'File[/etc/logrotate.d/syslog]' in
> parameter 'subscribe' (file:
> /etc/puppetlabs/code/environments/production/modules/base/manifests/syslog.pp,
> line: 21) on node lhcsrvmtrrsl01.fixnetix.com
>
> I want the logrotate command to run every time there is a change to the
> /etc/logrotate.d/syslog file.  Thought this could be achieved via the
> following:
>
>   exec { 'LogRotate':
> path=> '/usr/sbin',
> command => 'logrotate -vdf /etc/logrotate.d/syslog 2>/dev/null',
> subscribe   => File['/etc/logrotate.d/syslog'],
> refreshonly => true,
>   }
>
> I can't work out why the agent is complaining re Could not find resource
> 'File[/etc/logrotate.d/syslog]'
>
> # puppet resource file /etc/logrotate.d/syslog
> file { '/etc/logrotate.d/syslog':
>   ensure   => 'file',
>   content  => '{md5}e59f6816e9fcd21174501313720c660f',
>   ctime=> '2019-10-22 21:36:25 +0100',
>   group=> 0,
>   mode => '0644',
>   mtime=> '2019-10-22 21:36:25 +0100',
>   owner=> 0,
>   selrange => 's0',
>   selrole  => 'object_r',
>   seltype  => 'etc_t',
>   seluser  => 'system_u',
>   type => 'file',
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/482e3b96-c20c-4517-85c9-dc437f28c56c%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L7CBuB0bSZjc0pmosaCaCG_tud%3DmfknmbYen6sMaFTrig%40mail.gmail.com.

Re: [Puppet Users] Locking the version of Docker?

[Ben Ford]

It uses apt::pin like so,
https://github.com/puppetlabs/puppetlabs-docker/blob/7c7c38c09548b0e0ebdf92643f59efca93430e2b/manifests/repos.pp#L39-L43

On Fri, Sep 6, 2019 at 4:11 PM Stefan Lasiewski  wrote:

> Hi all,
>
> I'm using Puppet 5 to install Docker like so:
>
> class { 'docker':
>version => 5:18.09.9~3-0~ubuntu-bionic,
> }
>
>
> We'd like to control the version of Docker that's running using the Puppet
> manifest. That is, we want to prevent the unintentional upgrade of Docker
> when someone logs into the system and runs `apt upgrade`.
>
> The Docker module has an option named in_upstream_package_source
> ,
> but from the description, I'm a little unclear if this 'locks' or 'holds' a
> package version.
>
> Does the Docker module actually 'lock' the Docker package to a specific
> version?
>
> Thank you,
>
> -= Stefan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/d0e7e865-9b87-44bc-aa60-b071881078c0%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L7AuPJLG8n-ZtLAxR_0orxH9h1Qn3hR5_ALtS8S1kOy7g%40mail.gmail.com.

Re: [Puppet Users] Re: Using bash for custom facts - results are strings, not booleans

[Ben Ford]

> On Jul 23, 2019, at 7:49 AM, Jesse Hathaway  wrote:
> 
> The docs are still out of date on this supported feature.

One thing to note here is that whenever you find a docs page lacking, you can 
now provide feedback directly on the page. Just scroll to the bottom and give 
it a star ⭐️ rating. That will open a dialogue for you to provide suggestions 
for improvement.

Thanks for pointing this out! I'll make sure the team sees this.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/A7492CAC-BED9-415B-83A8-5D4F9453E952%40puppet.com.

Re: [Puppet Users] Using bash for custom facts - results are strings, not booleans

[Ben Ford]

If you just return a string, then that's how it's interpreted even if it
matches a keyword. To return a datatype, you'd need to return json.

echo '{"gdm_installed": true}'


and

echo '{"gdm_installed": false}'




On Thu, Jul 11, 2019 at 12:55 PM 'Prentice Bisbal' via Puppet Users <
puppet-users@googlegroups.com> wrote:

> I'm trying to use bash to create custom facts that are booleans,
> Unfortunately, when I do, the values are interpreted as strings, and not
> booleans. For example, here is my bash script, gdm.sh:
>
> #!/bin/bash
>
> PATH=/usr/bin:/bin:/usr/sbin:/sbin
>
> rpm --quiet -q gdm
> retval=$?
> if [ $retval -eq 0 ]; then
>  echo gdm_installed=true
> else
>  echo gdm_installed=false
> fi
>
> When I run the script, I get output in the following format, depending
> on whether or not the gdm package is installed on the node:
>
> gdm_installed=true
> gdm_installed=false
>
>  From everything I've read online, that should be sufficient, but when I
> run 'puppet facts, I see that the values for gdm_installed are strings
> and not booleans. For example:
>
> # puppet facts | grep false
>  "fips_enabled": false,
>  "gdm_installed": "false",
>  "clientnoop": false
>
>
> What am I doing wrong here? Is there something special about bash that
> prevents it from being used like this?
>
> --
> Prentice
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/883d5506-d9aa-8aa1-4904-89176566efac%40pppl.gov
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L63NeWyik17zwXKs7O5GM8GWZSzoGzTQmfGNiTMcwXRyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] pupperware experience and Console UI?

[Ben Ford]

>
> This is particularly painful in Dev/Test environments were PM
> installations are constantly rebuilt.


What are you testing in these environments? Eg, are you testing the
deployment of new infrastructure, including PE, or are you testing the
Puppet codebase? It might not be worth it to build & rebuild the master
each time.

That said, if you're not testing Enterprise features, then Pupperware is
totally usable for that purpose. I know several people who do similar
things, including one person who fires off a ton of containerized agents in
a Gatling-style load test.

And you are correct that the Pupperware stack is just the Open Source stack
right now. The team is also evaluating the feasibility of supporting
Enterprise too, but there's not a clear timeframe yet. What would you use
them for in your workflow?




On Mon, Jul 8, 2019 at 1:44 PM Michael Gale  wrote:

> Hello,
>
> Currently we run the latest LTS release of Puppet Enterprise in our
> Dev, QA and Production environments and have an automated installation of
> PM Enterprise working but are finding that process to be slow. This is
> particularly painful in Dev/Test environments were PM installations are
> constantly rebuilt.
>
> I found Puppet Docker images are available here:
> https://github.com/puppetlabs/pupperware and am considering switching
> over.
>
> Has anyone used these containers before and can share their feedback? I am
> not looking for Docker pros and cons. I am more interested in Puppet
> operations, upgrade issues, etc.
>
> Also am I correct in assuming that the Console GUI found in Puppet
> Enterprise is an Enterprise only feature and I would need to find a
> replacement for that component?
>
> Any feedback is appreciated.
>
>
> Thanks
>
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/270c9d2e-dc9f-4b64-9436-af0c9bbc1b29%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6eTgK1HmOCjxgs7CD514n9i%3Dvnw1o08OrOOu3Pq08JQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Coming to OSCON? You're invited to our Science Fair too

[Ben Ford]

The Puppet community has a lot of people with exciting Open Source tricks
up their sleeves. Are you interested in what they're hacking on or want to
share what you're hacking on?

An even bigger question…. Will you be in PDX for OSCON and want to come
have a good time?

Puppet is hosting a Science Fair party  in our
Portland home office the evening of July 17, 2019. Come have a drink and
poke at some new toys; see what fun projects people are working on. We’ve
got an Internet-enabled train layout, and will let you control the office
Spotify playlist with Bolt, our orchestration tool. What does all this even
mean? Come hang out and see!

We'll have a few stations set up for you to explore and get your hands
dirty with our Open Source projects. We'll have people sharing their own
home DIY projects. And we'll have table spots for community members to
showcase their own projects. Do you have something shiny to share?

Maybe most importantly, finger food, beer, and non-alcoholic refreshments
will be provided. Come hang with us. We'd love to see you and hear what
exciting things you've got going on.

Let us know if you plan to come  so we can make
sure to have enough food on hand.

 https://pup.pt/sciencefair 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6KcS_Vg56Q27yGrpbiNGK1%3DyJaOoR%2BMJX%2BPorKp2TUmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: rspec test issues

[Ben Ford]

Just a sanity check here. You did try the puppetlabs/firewall module before
writing your own, right? (https://forge.puppet.com/puppetlabs/firewall)

On Mon, Jul 1, 2019 at 6:40 AM Bill Sirinek  wrote:

> Fixed this by setting AUGEAS_LENS_LIB in spec/spec_helper_local.rb
>
> ENV['AUGEAS_LENS_LIB']='/opt/puppetlabs/puppet/share/augeas/lenses/dist'
>
>
>
> On Thursday, June 27, 2019 at 11:38:05 AM UTC-4, Bill Sirinek wrote:
>>
>> I need some help here. I have a simple augeas resource that changes a
>> line in the /etc/sysconfig/iptables-config file. I am trying to write an
>> rspec test for this and it's not working.
>>
>>
>>
>> RHEL7, pdk 1.10. I do not have any augeas packages installed, only using
>> what is bundled with pdk 1.10.
>>
>>
>>
>> If my augeas resource specifies the incl and lens attributes, the test
>> doesn't work at all, complaining that Shellvars.lns cannot be found.
>>
>>
>>
>> If my augeas resource specifies the context attribute and does not
>> specify a lens (augeas uses Shellvars for this file by default anyway), the
>> execute.with_change fails, but verifying the changes via aug_get and
>> checking execute.idempotently both succeed.
>>
>>
>>
>> Below I have the four combinations of the above and the output generated.
>> At the very bottom is my spec_helper.rb file.
>>
>>
>> The IPTABLES_MODULES value is "" in the iptables-config file in the
>> spec/fixtures/augeas/etc/sysconfig directory.
>>
>>
>> 1. Augeas resource specifying both incl and lens in manifest. Checking if
>> resource executes with change.
>>
>>
>>
>> Augeas resource:
>>
>>   augeas { 'set_iptables_modules':
>>
>> incl=> '/etc/sysconfig/iptables-config',
>>
>> lens=> 'Shellvars.lns',
>>
>> changes => [
>>
>>   "set IPTABLES_MODULES '\"iptable_nat ip_conntrack nf_nat_tftp 
>> nf_conntrack_ipv4\"'"
>>
>> ]
>>
>>   }
>>
>>
>>
>>
>>
>> Spec test:
>>
>>   describe_augeas 'set_iptables_modules', :lens => 'Shellvars', :target => 
>> 'etc/sysconfig/iptables-config' do
>>
>> it 'specifies the kernel modules to load in the iptables configuration' 
>> do
>>
>>   is_expected.to  
>> execute.with_change
>>
>>   expect(aug_get('IPTABLES_MODULES')) == '"iptable_nat ip_conntrack 
>> nf_nat_tftp nf_conntrack_ipv4"'
>>
>>   is_expected.to  
>> execute.idempotently
>>
>> end
>>
>>   end
>>
>>
>>
>>
>>
>> Output:
>>
>> bsirinek@mydevhost $ pdk test unit
>>
>> pdk (INFO): Using Ruby 2.4.5
>>
>> pdk (INFO): Using Puppet 5.5.12
>>
>> [✔] Preparing to run the unit tests.
>>
>> [✖] Running unit tests.
>>
>> Run options: exclude {:bolt=>true}
>>
>>   Evaluated 18 tests in 9.488949739 seconds: 1 failures, 0 pending.
>>
>> failed: rspec: ./spec/classes/init_spec.rb:29: Augeas[set_iptables_modules] 
>> fails when executing:
>>
>> debug: Opening augeas with root 
>> /tmp/rspec-puppet-augeas20190625-14571-apd4ov, lens path , flags 64
>>
>> debug: Augeas version 1.8.1 is installed
>>
>> warning: Loading failed for one or more files, see debug for /augeas//error 
>> output
>>
>> debug: /augeas/load/Xfm/error = Can not find lens Shellvars.lns
>>
>> debug: Will attempt to save and only run if files changed
>>
>> debug: sending command 'set' with params 
>> ["/files/etc/sysconfig/iptables-config/IPTABLES_MODULES", "\"iptable_nat 
>> ip_conntrack nf_nat_tftp nf_conntrack_ipv4\""]
>>
>> debug: Closed the augeas connection
>>
>> err: Could not evaluate: Saving failed, see debug
>>
>>   sebastion Augeas[set_iptables_modules] specifies the kernel modules to 
>> load in the iptables configuration
>>
>>   Failure/Error:
>>
>>
>>
>> describe_augeas 'set_iptables_modules', :lens => 'Shellvars', :target => 
>> 'etc/sysconfig/iptables-config' do
>>
>>   it 'specifies the kernel modules to load in the iptables 
>> configuration' do
>>
>> is_expected.to  
>> execute.with_change
>>
>> expect(aug_get('IPTABLES_MODULES')) == '"iptable_nat ip_conntrack 
>> nf_nat_tftp nf_conntrack_ipv4"'
>>
>>
>>
>> Total resources:   13
>>
>> Touched resources: 13
>>
>> Resource coverage: 100.00%
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 2. Augeas resource specifying only context and no lens in manifest.
>> Checking if resource executes with change.
>>
>>
>>
>> Augeas resource:
>>
>>   augeas { 'set_iptables_modules':
>>
>> context => '/files/etc/sysconfig/iptables-config',
>>
>> changes => [
>>
>>   "set IPTABLES_MODULES '\"iptable_nat ip_conntrack nf_nat_tftp 
>> nf_conntrack_ipv4\"'"
>>
>> ]
>>
>>   }
>>
>>
>>
>>
>>
>> Spec test:
>>
>>   describe_augeas 'set_iptables_modules', :lens => 'Shellvars', :target => 
>> 'etc/sysconfig/iptables-config' do
>>
>> it 'specifies the kernel modules to load in the iptables configuration' 
>> do
>>
>>   is_expected.to  
>> execute.with_change
>>
>>   expect(aug_get('IPTABLES_MODULES')) == 

[Puppet Users] Coming to OSCON? Stop by our Science Fair too!

[Ben Ford]

The Puppet community has a lot of people with exciting Open Source tricks
up their sleeves. Are you interested in what they're hacking on or want to
share what you're hacking on?

An even bigger question…. Will you be in PDX for OSCON and want to come
have a good time?

Puppet is hosting a Science Fair party  in our
Portland home office the evening of July 17, 2019. Come have a drink and
poke at some new toys; see what fun projects people are working on. We’ve
got an Internet-enabled train layout, and will let you control the office
Spotify playlist with Bolt, our orchestration tool. What does all this even
mean? Come hang out and see!

We'll have a few stations set up for you to explore and get your hands
dirty with our Open Source projects. We'll have people sharing their own
home DIY projects. And we'll have table spots for community members to
showcase their own projects. *Do you have something shiny to share*?

Maybe most importantly, finger food, beer, and non-alcoholic refreshments
will be provided. Come chill with us. We'd love to see you and hear what
exciting things you've got going on.

*Let us know if you plan to come * so we can
make sure to have plenty of food on hand.

https://pup.pt/sciencefair, or shout at me for any questions.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5noSYVBKhB5Xg574stt9yENwwHD%3DjmZA9WHB9wFo-T9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

[Ben Ford]

Yes. A class without a namespace must be named the same as the module
containing it, *and be in the init.pp file*.

In other words, your /opt/puppetlabs/puppet/modules/adhoc/manifests/*adhoc*
.pp file should be /opt/puppetlabs/puppet/modules/adhoc/manifests/*init*.pp.

See https://puppet.com/docs/puppet/latest/modules_fundamentals.html for
more information.

On Fri, Jun 14, 2019 at 1:06 PM lhu  wrote:

> Hi John,
>
> Would you have any idea why this would fail
> file
> #puppet parser validate adhoc.pp
> Warning: Unacceptable location. The name 'adhoc' is unacceptable in file
> '/opt/puppetlabs/puppet/modules/adhoc/manifests/adhoc.pp' (file:
> /opt/puppetlabs/puppet/modules/adhoc/manifests/adhoc.pp, line: 1, column: 1)
>
> adhoc.pp file:
>
> class adhoc {
>
>
> }
>
> I put the file under
> /opt/puppetlabs/puppet/modules/adhoc/manifests
> this is running puppet 5.5 on a new install
>
> Thanks,
> Leo
>
> On Wednesday, August 29, 2018 at 9:58:32 AM UTC-4, Henrik Lindberg wrote:
>>
>> On 2018-08-29 15:11, jcbollinger wrote:
>> >
>> >
>> > On Tuesday, August 28, 2018 at 12:13:15 PM UTC-5, kris.b...@puppet.com
>> > wrote:
>> >
>> >
>> > Hi Jon,
>> >
>> > As you have read, this is part of our work implementing errors to
>> > enforce the standards set down in PUP-1434.  In particular, your
>> > example '$module_path/seed/manifests/init.pp' looks like it is in
>> > the init file of module 'seed'.  Assuming that is what you meant,
>> > anything starting with 'seed' would be OK in that file, e.g.
>> 'seed',
>> > 'seed::remote_file', 'seed::foo::remote_file' would all work.  Note
>> > that as part of point 4. of PUP-1434 (now being implemented in the
>> > work of PUP-9020), you will also not be allowed to put things like
>> > resources in the top level, but instead should include your
>> > resources in a class, define, function, or type declaration.
>> >
>> >
>> > As a matter of style, the usual recommendation is that furthermore,
>> > every class and defined type definition be located in its own file
>> > ,
>> > named as predicted from its fully-qualified name.  Of course, this is
>> > coupled with assigning an appropriate fully-qualified name.  It is
>> > important to understand that class and type names in Puppet are
>> > independent of the pathnames of the files in which the class and type
>> > definitions appear.  The importance of the pathnames is limited to
>> > enabling Puppet to /find/ type and class definitions at runtime.
>> >
>> >
>>
>> Not quite - what is now starting to be enforced is that definitions
>> must be made in a file that is on an accepted path for that definition.
>>
>> Best,
>> - henrik
>>
>> > John
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Puppet Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to puppet...@googlegroups.com
>> > .
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/puppet-users/916271cc-6a49-4374-afe2-d6fe0dff297d%40googlegroups.com
>> > <
>> https://groups.google.com/d/msgid/puppet-users/916271cc-6a49-4374-afe2-d6fe0dff297d%40googlegroups.com?utm_medium=email_source=footer>.
>>
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>>
>> Visit my Blog "Puppet on the Edge"
>> http://puppet-on-the-edge.blogspot.se/
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/dc9b55e8-f5c3-4622-a223-0d5df43e36db%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5%2BdRHBapgkatd8Leu7-B5L5eVDNjSxLeD-cT%2BBVB1yAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] switching from source => "puppet:/// to source => "file:///

[Ben Ford]

I suspect that you're misunderstanding something about how Puppet works, 
because as far as I can tell, you're trying to copy 
/etc/apache2/conf.d/testpuppet.conf to /etc/apache2/conf.d/testpuppet.conf. 
(The same path)

It's relatively rare to use anything but a puppet:// URI in a file source 
attribute.

I suggest running through the learning VM to get a quick taste of how the 
system works. https://learn.puppet.com


Sent from my iPhone

> On Jun 13, 2019, at 4:29 AM, Locke Hajo  wrote:
> 
> /etc/apache2/conf.d/testpuppet.conf

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/37B1C8A3-DCED-44D5-8A56-D2EE9E5AB213%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] facter to return version of an installed package

[Ben Ford]

You cannot pass a variable to facter, because that's not how its model is
designed. Facter is a tool that runs to gather relatively static system
information, called facts. A fact with a given name has a given value. In
other words, you need one unique fact for every value you're gathering.
(though it can be nested into a data structure if needed.)

This is generally considered an anti-pattern in most cases. If you're
reactive then your configuration rules aren't prescriptive. In other words,
you cannot look at your code and predict what it will do. This means that
your configuration isn't repeatable and you get yourself back into the bad
old days where nobody really knew *for sure* what was on any given machine,
or if it would even boot up again if you brought it down.

Instead, you should prescribe the version of the package in question. In
other words, move away from "if $package is version 1, then use config A,
and if it's version 2 use config B" to "this node should be package version
2 with config B."

To be sure, this pattern doesn't always work and you don't always have
control over the full system. What's your use case that you're trying to
solve?

On Tue, May 14, 2019 at 2:19 AM Helmut Schneider  wrote:

> Hi,
>
> before I reinvent the wheel:
>
> Does anyone know a custom fact that returns the version of an installed
> package (if it is installed)?
>
> I assume it would be something like
>
> Facter.add(:package_version) do
>   setcode do
> osfamily = Facter.value(:osfamily)
> case osfamily
> when /ubuntu|debian/
>   Facter::Util::Resolution.exec("dpkg -l '*$my_package*' | grep
> ^ii")
> when 'freebsd'
>   Facter::Util::Resolution.exec("pkg info -ix $my_package*")
> end
>   end
> end
>
> but I have not found out yet how to pass a variable to facter.
>
> helmut@ubuntu:~$ puppet -V
> 6.4.2
> helmut@ubuntu:~$ facter -v
> 3.13.2
> helmut@ubuntu:~$
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/xn0ltx8j23azj63000%40news.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6hoBP57eqVh4wxUNTbZY8xkJQ08shm1S3aN7QjcwyR3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Replace some text

[Ben Ford]

It looks like what you're trying to do is inline editing of /etc/bashrc,
but still let people poke at it themselves. That's a fragile position to be
in. For example, given your regex solution, what's to stop someone from
doing something like innocently defining their $PS1 iteratively? Something
like this made up example:

PS1=$(run some command)
> PS1="$(run some other command)/${PS1}"
> export PS1="(${PS1}) \u@\h: \W: "


Or maybe they want to set another variable, maybe something like:

export UPS1_STATE="some such or other"


You'll end up with garbled variables at best, or a crashed script and then
complaints that you broke their system. (maybe you'll even get lucky and
they'll be tickets! lol)

Instead, a far far far more maintainable pattern is for you to flat out own
/etc/bashrc, but to source a second  /etc/bashrc.local user editable file
from within. That lets you manage it as a template which will give you a
known and repeatable output, and let the users do their own customization
in a place that they own, meaning that they also own any failures they
create.


On Mon, Apr 8, 2019 at 10:23 AM KRouth Clinipace 
wrote:

> Question - is it possible to use the puppet regsubst function in place of
> the exec used here (to save spawning a new shell process) ?
> kevin
>
> On Friday, May 21, 2010 at 10:28:58 PM UTC-4, Marley Bacelar wrote:
>>
>> Nice... I solved my probleman using the:
>>
>> define replace($file, $pattern, $replacement) {
>>   exec { "/usr/bin/perl -pi -e 's/$pattern/$replacement/' '$file'":
>>   onlyif => "/usr/bin/perl -ne 'BEGIN { \$ret = 1; } \$ret = 0 if
>> /$pattern/ && ! /$replacement/ ; END { exit \$ret; }' '$file'",
>>}
>> }
>>
>> Then i my class used:
>>
>> replace { "/etc/bashrc":
>>file => "/etc/bashrc",
>>pattern => "PS1",
>>replacement => "PS1 DOMAINA.COM"
>> }
>> Worked perfectly... Know i will see the other options proposed here.
>> Thank you evry much guys
>>
>> --
>> Marley Bacelar
>> Project Fedora Ambassador
>> VCP, VSP. VTSP., ITILF, IBM 000-076, IBM 000-330, IBM 000-331
>> marley...@gmail.com
>>
>> 2010/5/21 R.I.Pienaar 
>>
>>> > The vast majority of our text replacement work we do is for files that
>>> > have simple key/value pairs with an assignment operator.
>>> >
>>> >
>>> > foo=bar
>>> > foo: bar
>>> >
>>> >
>>> > etc.
>>> >
>>> >
>>> > We occasionally stray outside this with a regexp replacer, but I
>>> > totally agree with Daniel here, it's not the most robust thing in the
>>> > world.
>>> >
>>> >
>>> > Generally we do this because we want to allow people to customize
>>> > extra parts of their config files, and we've switched daemons entirely
>>> > for some services, simply based upon their ability to cope with a
>>> > parts.d directory or to have "include" directives of some kind.
>>> >
>>> >
>>> > That allows you to ship an absolute config with a default include that
>>> > people are free to modify.
>>> >
>>>
>>>
>>> fwiw, the newest version of my concat module supports symlinking into a
>>> concat file, so if you have a config file that you would like users to drop
>>> settings it and you want them to only do so in a very specific place in a
>>> file you can now achieve that by building your config file and including a
>>> user editable file right where you want it.
>>>
>>> Very nice feature to give users some rights without loosing control of
>>> the file or its structure.
>>>
>>> It wouldn't be too hard to extend it to make arbitrary user supplied .d
>>> directories for daemons that dont support those :)
>>>
>>> http://github.com/ripienaar/puppet-concat
>>>
>>>
>>> --
>>> R.I.Pienaar
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> To unsubscribe from this group, send email to puppet...@googlegroups.com
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet...@googlegroups.com.
>> To unsubscribe from this group, send email to puppet...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/efa23924-e6eb-4338-bdb6-648d01923cee%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are 

Re: [Puppet Users] Registry module not working

[Ben Ford]

Can you include the actual error message along with this snippet of the
stack trace?

Also Puppet 3.x went EOL 787 days ago on December 31, 2016. You should
REALLY consider upgrading, especially since your master has already been
upgraded. It's generally recommended to run the same versions of master &
client.

On Mon, Feb 25, 2019 at 11:22 AM SUDISH MADATHIL 
wrote:

> *Error:
> /Stage[main]/Firewallon/Registry_value[hklm\Software\Pluralsight1\PuppetO*
> *nWindows]: Could not evaluate: undefined method `RegQueryValueExW' for
> Puppet::U*
> *til::Windows::Registry:Module*
>
> Issue when trying to use registry module specific to updating values in
> registry. Can you help with this message?
>
> Puppet master version : - 4.10.12
> Puppet client/agent version :- 3.8.7
>
> Trace logs: -
>
> >>
>
>
> C:/ProgramData/PuppetLabs/puppet/var/lib/puppet/provider/registry_value/registry
> .rb:38:in `block (2 levels) in exists?'
> C:/Program Files/Puppet
> Labs/Puppet/puppet/lib/puppet/util/windows/api_types.rb:
> 30:in `block in from_string_to_wide_string'
> C:/Program Files/Puppet
> Labs/Puppet/puppet/lib/puppet/util/windows/api_types.rb:
> 26:in `initialize'
> C:/Program Files/Puppet
> Labs/Puppet/puppet/lib/puppet/util/windows/api_types.rb:
> 26:in `new'
> C:/Program Files/Puppet
> Labs/Puppet/puppet/lib/puppet/util/windows/api_types.rb:
> 26:in `from_string_to_wide_string'
>
> C:/ProgramData/PuppetLabs/puppet/var/lib/puppet/provider/registry_value/registry
> .rb:37:in `block in exists?'
> C:/Program Files/Puppet
> Labs/Puppet/sys/ruby/lib/ruby/2.0.0/win32/registry.rb:38
> 9:in `open'
> C:/Program Files/Puppet
> Labs/Puppet/sys/ruby/lib/ruby/2.0.0/win32/registry.rb:49
> 6:in `open'
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/bb2a3fcc-6762-4194-bfb0-7b67e3a398ae%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L78gUxJXPEZ1NO4rAMPD4eVpQJW_7T9htBP81HNJBoEXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Using lvicainne-bashrc -

[Ben Ford]

You don't explain how you classified your nodes. Creating modules just
makes the classes, they don't have any effect until you actually use them
via classifying nodes. See
https://puppet.com/docs/puppet/latest/lang_classes.html#declaring-classes
for more information.

You asked why the stdlib module said (???). See how it doesn't say
puppetlabs-stdlib either?  That means that it's not
http://forge.puppet.com/puppetlabs/stdlib. I don't know what it is, but
it's not that :)



On Wed, Feb 20, 2019 at 1:34 PM  wrote:

> All,
>
>
> I'm not sure if this is the correct venue for this question, but...
>
> I have a puppetserver v. puppet5-release-5.0.0-4.el7.noarch on Centos7.  I
> manage several environments and was able to install and manage to get
> working lvicainne-bashrc (to 'push' out .bashrc files) in our TEST
> environment.  Thinking I had it made - I attached the module to one of our
> production environments in the exact same manner as I did with the test
> environment.
>
> None of the servers in the production environment picked up the new bashrc
> files.  It's as if I had done nothing at all to the production
> environment.  I checked
> /opt/puppetlavs/server/data/puppetserver/reports/{servername} and there is
> no mention of "bash" or "bashrc" in any of the reports (except for the one
> server in the test environment).  Is there anywhere else I can look to
> determine if there is an error?  I've looked at other logs, but to no avail.
>
> Here's my puppet module list:
>
> [root@puppetserver reports]# puppet module list --tree
> /etc/puppetlabs/code/environments/production/modules
> ├─┬ puppetlabs-accounts (v3.0.0)
> │ ├── puppetlabs-translate (v1.1.0)
> │ └── puppetlabs-stdlib (v4.24.0)
> ├── accounts1 (???)
> ├── production (???)
> ├── accounts2 (???)
> └─┬ puppetlabs-postgresql (v5.3.0)
>   ├── puppetlabs-apt (v4.5.1)
>   └── puppetlabs-concat (v4.2.0)
> /etc/puppetlabs/code/modules
> ├─┬ puppetlabs-accounts (v1.3.0)
> │ └── puppetlabs-stdlib (v4.24.0)
> [/etc/puppetlabs/code/environments/production/modules]
> ├─┬ lvicainne-bashrc (v0.0.7)
> │ └── puppetlabs-concat (v4.2.0)
> [/etc/puppetlabs/code/environments/production/modules]
> ├── accounts1(???)
> ├── opsaccounts2(???)
> ├── production (???)
> ├── accounts3 (???)
> ├── opsaccounts (???)
>
├── stdlib (???)
> ├── accounts4 (???)
> └── puppetlabs-apt (v4.5.1)
>
/opt/puppetlabs/puppet/modules
> ├── accounts (???)
> ├── accounts1 (???)
> ├── accounts2 (???)
> └── stdlib (???)
>
> You can see the ones that were created by hand have (???) for the version
> number.  I understand that - why is stdlib showing a (???).  Is that
> possibly related to my issue?
>
> FYI - lvicainne-bashrc have a dependency of stdlib and concat.
>
>
> Thanks in advance.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/c0d7a6b1-da12-43d0-afa1-247cfa8a32d1%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5hPjeZhkBk%2BR-FnyK8fdwbc8GgN4qgA9umMoagXS15kg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] [augeas] edit YAML file

[Ben Ford]

The https://forge.puppet.com/fiddyspence/hash_file module makes it very easy to 
manage yaml files.

Sent from my iPhone

> On Feb 7, 2019, at 4:47 PM, Helmut Schneider  wrote:
> 
> Hi,
> 
> I want to edit a YAML file:
> 
> network:
>  version: 2
>  renderer: networkd
>  ethernets:
>eth0:
>  dhcp4: yes
>  dhcp6: yes
> 
> Id like to add a line:
> 
> network:
>  version: 2
>  renderer: networkd
>  ethernets:
>eth0:
>  dhcp4: yes
>  dhcp6: yes
>  dhcp-identifier: mac
> 
> How can I do so?
> 
> Thank you!
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/xn0lpwsm9ld5lb8000%40news.gmane.org.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/55259A86-56F3-446C-81B0-BBCD7B4A90ED%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Push Puppet custom Facts to agent

[Ben Ford]

Put your facts in a module and they'll be synced everywhere they're needed
automatically.
https://puppet.com/docs/puppet/5.3/plugins_in_modules.html#auto-download-of-agent-side-plug-ins-pluginsync

On Thu, Jan 31, 2019 at 4:48 AM Nikhil Patil 
wrote:

> Hi All,
>
> I have created the custom fact in ruby and placed in facterlib path on
> master. when i run facter -p on master i see the facter value in response.
> Now i want this to be pushed on all my agent from puppet master. how this
> can be achieved.
>
> Thanks & Regards
> Nikhil
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/f69c0165-5a41-45a5-a2b2-8837d7374a8c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4uZZuUW0fjhsVsEzWv7KkrJhGdGZV3mPcZW%3DNjHdV-eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: ensure_packets not working

[Ben Ford]

Sharing the code that you're working with will make it possible for people
to help solve your problem.

On Wed, Jan 30, 2019 at 10:22 AM Jochen Haeberle 
wrote:

> Hi @all,
>
> does anyone have an idea what could be happening? I think this might be
> some sort of configuration error on the node, on the other hand, puppet
> obviously seems able to compile a catalog.
> What could be the reason for such a difference in behaviour on Debian 9.7
> either on Vagrant or VMware?
>
> Thanks for any hints, regards
>
> Jochen
>
> Am Dienstag, 29. Januar 2019 00:02:42 UTC+1 schrieb Jochen Haeberle:
>>
>> Hi,
>>
>> I am using serverless puppet apply on some nodes. I prepared a set of
>> manifests using forge plugins. I developed everything using Vagrant quite
>> fine.
>>
>> Now I put my code via git on a debian 9.7 VM with puppet 6.2 and am
>> getting the following errors:
>>
>> Error: Evaluation Error: Error while evaluating a Function Call,
>> Duplicate declaration: Package[libapache2-mod-php7.3] is already declared
>> at (file:
>> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/apache.pp,
>> line: 78); cannot redeclare (file:
>> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>> line: 24) (file:
>> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>> line: 24, column: 3)
>>
>> Both instances use the stdlib function ensure_packages. If I remove one
>> of the instances, I will get the error with another package.
>>
>> puppetlabs/stdlib and all other modules are up to date, thanks to r10k,
>> Code is working on a fresh vagrant machine.
>>
>> What can be the culprit of this? I have no idea where to look for this
>> problem.
>>
>> Thanks in advance vor any hints, regards
>>
>> Jochen
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/4e0cd8c4-577f-42a6-a664-e6f4015fca5d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6%2BztyfNgf3s7uz0y5FvZ%2BmFbFWrA9Bo0e4YoK%2Bf%2BndKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Replacing extlookup to look up external things!

[Ben Ford]

Your simplest and most straightforward upgrade path would be to port the
CSV file to a common.yaml file and then switch to using lookup() with
hieradata. Later on, you can start differentiating and build a sane data
hierarchy.

Check out the docs at https://puppet.com/docs/puppet/latest/hiera_quick.html



On Tue, Jan 29, 2019 at 2:45 PM Robert Inder 
wrote:

> I'm looking at the possibility of moving our Puppet manifests from 3.8 to
> Something More Recent (i.e. 6.1)
>
> We have one big CSV file for (mostly) encrypted passwords and the like.
> And our existing manifests use extlookup to extract the relevant entries,
> via calls like pw =
>
> How should I replace this?
> Can someone point me at an example of the simplest possible external
> lookup?
>
> Robert.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/7d2122c0-72bf-467f-a7d0-cdac4617504b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6ciVd_FGU7x6Sg%3D-TVpy_rhk1fTW6da31nLNv9XCjNFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Ask Puppet sunset

[Ben Ford]

After 6 years of Ask.Puppet.com, we are closing the site down on February
first. We are directing folks to use the Puppet Community Slack
 instead. The existing content is archived so
existing bookmarks will continue to work, but new questions, answers, or
comments will not be accepted.

We understand that this might be disappointing for some of you. Ask Puppet
was launched in 2013 as a permanent home for questions and answers about
Puppet. However with passing time, the way in which people asked questions
has changed too. We believe that you will have a better experience by
asking questions in real time in the Puppet Community Slack
.

In place of Ask, we have instituted a few programs that we think might be
of interest to you. Our Office Hours
 are regular Slack based Q
sessions that provide you the opportunity to ask Puppet experts any
questions you have or provide any feedback you'd like. They're topic based,
so that you always know what the scope of the conversations can be. These
sessions are completely open to the world, so stop by the Slack
#office-hours

channel and chat!

We've also enabled the Foqal Q bot  on Slack and
imported all the Puppet Docs and the existing Ask Puppet answers. It might
automatically answer your question in channel, but if it doesn't you can
always try direct messaging it your question.

The Google Group mailing lists and other mediums will continue to exist.
You're welcome to seek out assistance in any of these spaces.


   -

   puppet-users mailing list
   
   -

   https://stackoverflow.com
   


We want to thank everyone who has participated on Ask and helped our
community out. Each and every one of you rock.


TOP CONTRIBUTORS -- Thanks!


   - [image: GregLarkin gravatar image]
   
   GregLarkin 
   4932 ●5 ●22 ●64http://www.puppet.com/
   - [image: ramindk gravatar image]
   
   ramindk 
   4606 ●54 ●71 ●126
   - [image: llowder gravatar image]
   
   llowder 
   2952 ●17 ●36 ●72http://blog.keepingyou...
   
   - [image: Ancillas gravatar image] 
   Ancillas 
   2828 ●19 ●39 ●71http://www.techgamelif... 


See you on Slack  and happy puppeteering!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L7pbQBKWFGWmR5WNz6FZkkBqa3adC72YqUmnavsrUdNLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] relationships, ordering, and defined types

[Ben Ford]

Caps all segments in a defined type name:

before => Bar::Baz['qux'],


On Tue, Jan 22, 2019 at 2:20 PM Matt Zagrabelny  wrote:

> Greetings!
>
> I'm running puppet 5.5 on Debian Buster.
>
> This exists:
>
> define bar::baz() {
> file { "/tmp/$name": }
> }
>
> ...somewhere else...
>
> bar::baz { 'qux': }
>
> file { '/tmp/foo':
> before => Bar::baz['qux'],
> }
>
> But when the catalog gets compiled I get an error:
>
> Evaluation Error: Error while evaluating a Resource Statement, Illegal
> class reference
>
> Is it possible to use a defined type with a "before" (or any other
> relationship metaparameter) ?
>
> Thanks!
>
> -m
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/CAOLfK3V7E47VzhjNSznYTC_UuH%3DK44GsgLuH9y4vnTFy70i5QA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6iaXfFhz8%3D4QK2YM0iMufJb8NaicOTvYVGg5LY1%2BhK5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] resolve hostname via custom fact

[Ben Ford]

>
> I want to resolve a hostname via a custom fact:
> require "resolv"
> Facter.add("puppet_master_ip") do
>   setcode do
> Resolv::DNS.open(:nameserver => ['8.8.8.8']) do |dns|
>   ip = dns.getaddresses("www.puppet.org")
> end
>   end
> end
> How do I get the output? I just want to get the first IP.


Ruby has a habit that it picked up from its Perl ancestor of implicitly
returning the last expression from a block or function. That's a neat
shortcut, but that's also why you see so much Ruby code that just seems to
stop and doesn't show returning of data. Because it's the last expression
evaluated, your fact is simply returning an array of Resolv objects, which
Facter doesn't know what to do with.

To make your code work, you just need to do two things:

require "resolv"
Facter.add("puppet_master_ip") do
  setcode do

*ip = nil # Declare your variable outside the block to keep its
scope available*Resolv::DNS.open(:nameserver => ['8.8.8.8']) do |dns|
  ip = dns.getaddresses("www.puppet.org")
end

*ip.first.to_s# implicitly return the string value of the first
item*  end
end

You should also put your fact in a module and let Puppet pluginsync it
automatically. You'll need to run facter with the -p flag.
https://puppet.com/docs/puppet/latest/plugins_in_modules.html#adding-plug-ins-to-a-module

Cheers!

On Sun, Dec 23, 2018 at 7:25 AM Helmut Schneider  wrote:

> Hi,
>
> I want to resolve a hostname via a custom fact:
>
> require "resolv"
>
> Facter.add("puppet_master_ip") do
>   setcode do
> Resolv::DNS.open(:nameserver => ['8.8.8.8']) do |dns|
>   ip = dns.getaddresses("www.puppet.org")
> end
>   end
> end
>
> How do I get the output? I just want to get the first IP.
>
> helmut@h2786452:~$ facter puppet_master_ip
> [
>
> ]
> helmut@h2786452:~$ facter puppet_master_ip --debug --trace
> 2018-12-23 16:22:57.816747 INFO  puppetlabs.facter - executed with
> command line: puppet_master_ip --debug --trace.
> 2018-12-23 16:22:57.820403 INFO  leatherman.ruby:138 - ruby loaded from
> "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0".
> 2018-12-23 16:22:57.880073 INFO  leatherman.ruby:187 - using ruby
> version 2.1.9
> 2018-12-23 16:22:57.880231 INFO  puppetlabs.facter - requested queries:
> puppet_master_ip.
> 2018-12-23 16:22:57.880317 DEBUG puppetlabs.facter - fact
> "facterversion" has resolved to "3.6.10".
> 2018-12-23 16:22:57.880364 DEBUG puppetlabs.facter - fact
> "aio_agent_version" has resolved to "1.10.14".
> 2018-12-23 16:22:57.881923 DEBUG leatherman.file_util:65 - Error
> reading file: No such file or directory
> 2018-12-23 16:22:57.882710 DEBUG puppetlabs.facter - loading all custom
> facts.
> 2018-12-23 16:22:57.882751 DEBUG puppetlabs.facter - loading custom
> fact directories from config file
> 2018-12-23 16:22:57.883863 DEBUG puppetlabs.facter - searching for
> custom facts in /opt/puppetlabs/puppet/lib/ruby/site_ruby/2.1.0/facter.
> 2018-12-23 16:22:57.884066 INFO  puppetlabs.facter - loading custom
> facts from
> /opt/puppetlabs/puppet/lib/ruby/site_ruby/2.1.0/facter/external_ip4.rb.
> 2018-12-23 16:22:57.962679 INFO  puppetlabs.facter - loading custom
> facts from
> /opt/puppetlabs/puppet/lib/ruby/site_ruby/2.1.0/facter/puppet_master_ip.
> rb.
> 2018-12-23 16:22:58.295668 DEBUG puppetlabs.facter - fact
> "external_ip4" has resolved to "81.169.210.177".
> 2018-12-23 16:22:58.555197 DEBUG puppetlabs.facter - fact
> "puppet_master_ip" has resolved to [
>
> ].
> 2018-12-23 16:22:58.555380 DEBUG puppetlabs.facter - skipping external
> facts for "/home/helmut/.puppetlabs/opt/facter/facts.d": No such file
> or directory
> 2018-12-23 16:22:58.555445 DEBUG puppetlabs.facter - skipping external
> facts for "/home/helmut/.facter/facts.d": No such file or directory
> 2018-12-23 16:22:58.555478 DEBUG puppetlabs.facter - no external facts
> were found.
> [
>
> ]
> helmut@h2786452:~$
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/xn0lj1k498fj8t8000%40news.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5Mrusp%3DhZ%2BFUKswkaKv38fPRAvA2vqNtviC8AMEV0j%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] exec and variables

[Ben Ford]

Sure. When you make a reference (the upper case File syntax), it has to
point to a thing that exists. The reference is a resource type (File) and a
resource title (99-status.conf), but you've not defined a resource with
that title. Basically, it's like making a symlink to a file that doesn't
exist. To fix it, you just need to change your code so the reference and
the resource title agree on a title.

Read more about relationships at
https://puppet.com/docs/puppet/5.5/lang_relationships.html and about the
reference syntax at
https://puppet.com/docs/puppet/5.5/lang_data_resource_reference.html

On Thu, Dec 20, 2018 at 8:56 AM Helmut Schneider  wrote:

> Hi,
>
> I want to exec something with a variable. If found the following link
> and tried to implement:
>
>
> https://stackoverflow.com/questions/33557093/puppet-notify-a-class-with-parameters
>
>   file { "${apacheConfPath}/conf-available/${file}":
> mode   => '0640',
> owner  => $rootUID,
> group  => $rootGID,
> source =>
>
> "puppet:///modules/my_apache/${operatingsystem}/${apacheConfPath}/conf.d/${file}",
> #notify => a2enmod["$file"],
> #notify => a2enmod['99-status.conf'],
>   }
>   exec { "a2enconf_${title}":
> path=> '/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin',
> refreshonly => true,
> command => "a2enconf ${title}",
> #subscribe   => File['99-status.conf'],
> subscribe   => File["$file"],
>   }
>
> Error: Failed to apply catalog: Could not find dependency
> File[99-status.conf] for Exec[a2enconf_my_apache::config_files] at
> /etc/puppetlabs/code/modules/my_apache/manifests/config_files.pp:130
>
> Can someone point me to the right direction?
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/xn0lixerc48gqno000%40news.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L72V-VAmPWFZ%3DvMJOYts0RdTiDR0GRssS%3Dw1Md70%2BRimQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet.agent with path

[Ben Ford]

Rafael, if you're trying to execute scripts with a certain path, you'd
provide that at the resource declaration level, like so:

exec { 'tar -xf /Volumes/nfs02/important.tar': cwd => '/var/tmp', creates
=> '/var/tmp/myfile', path => ['/usr/bin', '/usr/sbin',], }

See this for more information:
https://puppet.com/docs/puppet/latest/types/exec.html#exec-attribute-path

On Wed, Nov 28, 2018 at 10:18 AM Eric Sorenson  wrote:

> Sorry Rafael, I don't understand what you're asking. Can you share the
> puppet code that you are trying to use, and the error message you get?
>
> --eric0
>
> On Wednesday, November 28, 2018 at 5:54:34 AM UTC-8, Rafael Tomelin wrote:
>>
>> Hi,
>>
>> How configure path in puppet.agent.
>>
>> I need path = source /etc/profile . , how configuration this path?
>> --
>>
>> Atenciosamente,
>>
>> Rafael Tomelin
>>
>> skype: rafael.tomelin
>>
>> E-mail: rafael.tome...@gmail.com
>>
>> RHCE  - Red Hat Certified Engineer
>> PPT-205 - Puppet Certified Professional 2017
>> Zabbix- ZABBIX Certified Specialist
>> LPI3
>> ITIL v3
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/5c0f935e-c0ff-4202-b48c-79a316f69c87%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5vqSVtZTkY%2B9HF_7MS7naEbvjSPk8C-wR-BQ98K4cZ9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] pip package provider on Redhat

[Ben Ford]

Hi Sergei!

Puppet 3.x is quite old, and in fact has been end-of-lifed for 655 days as
of today! (December 31, 2016). It is no longer receiving security or bug
fixes. If you upgrade to a modern version, you'll see that there's are new
pip and pip3 providers that use the appropriate commands.
https://github.com/puppetlabs/puppet/blob/1707f2ca46867651095e01379bd01dab08076b8b/lib/puppet/provider/package/pip.rb#L55-L65


On Wed, Oct 17, 2018 at 11:18 AM Sergei Gerasenko  wrote:

> Hello,
>
> I'm running puppet 3.5.1 and the pip package provider has this bit:
>
>   def self.cmd
> case Facter.value(:osfamily)
>   when "RedHat"
> "pip-python"
>   else
> "pip"
> end
>   end
>
> As you can see, when the OS is RedHat, it wants to use the pip-python
> command, but it's not available for latest versions of Redhat/CentOS. Is
> there an easy way to override the command for that provider without
> altering the puppet source code?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/c15b51cd-23fa-4406-ad92-ff3e2b63c839%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5T6hPMdmQYQ0sVQCsZTUdxsrrufjXmUa07KqhQr%3D%2B9Cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] modulo, exec or provider customization

[Ben Ford]

Hi Rafael. You would not have any need to create a custom provider.
Depending on which database server you're using and what the end result
that you're trying to achieve is, you can use built-in resource types to do
what you want.

For example, with MS SQL Server, you can evaluate TSQL queries with
https://forge.puppet.com/puppetlabs/sqlserver/types#sqlserver_tsql
And with MySQL, you could use a resource type to instantiate a database
using an .sql file with
https://forge.puppet.com/puppetlabs/mysql/reference#sql
or you could use a Task to arbitrarily execute SQL statements with
https://forge.puppet.com/puppetlabs/mysql/tasks#task_sql

And if all else fails, you could simply use a file resource to put your
file on the node and use an exec to evaluate it.

On Wed, Oct 17, 2018 at 12:06 AM Rafael Tomelin 
wrote:

> Folks,
>
> I was given a task to deploy and update an application via Puppet, yes it
> must be via Puppet at that time. A company has units scattered around the
> world, about 32 units running the same application on different servers.
>
> One of the characteristics is that sometimes there are some types of SQL
> (computer) files and must follow an order:
> new_table.sql
> alter_table_YYMD.sql
> delete_table.sql
> procedure_table.sql
> view_table.sql
>
> In addition, some files are required as system files (js, img, css, php,
> tpl, html), since the directories are already correct.
>
> My biggest problem is in the SQL execution order and then in creating a
> provider.
>
> Ideally, would you create a provider for each type of SQL or one that all
> SQL?
> --
>
> Atenciosamente,
>
> Rafael Tomelin
>
> skype: rafael.tomelin
>
> E-mail: rafael.tome...@gmail.com
>
> RHCE  - Red Hat Certified Engineer
> PPT-205 - Puppet Certified Professional 2017
> Zabbix- ZABBIX Certified Specialist
> LPI3
> ITIL v3
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/CAGEUqbBx17yQa3hVpmf%2BQHvyOFL6dL6PzYwgwHKxiak38ZhmLA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6TH-kpMENU5wpwhDvP6LQQOY55fS2x1MGvssqGg5Ai6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: New Deferred type and agent data lookups in Puppet 6

[Ben Ford]

In general, you're going to want to be cautious about using agent-side
functions. It might be simpler to gather information during run time in
some cases, but it makes your catalog more black-box and unpredictable.
Here are just a couple concerns:

You lose some of the ability to look at the facts and look at the code and
know what the outcome will be because the enforcement also depends on the
output of some lazy bound agent function. For example, if you have code
that uses the $hostname fact, you can validate that the $hostname fact
actually resolved to something useful and raise an error if not. You can
even fail the compile and enforce the last cached catalog until you can fix
it. If that were an agent side function, you won't have any warning before
things break.

You also make your catalogs less repeatable. For example, if you push out a
codebase update and it doesn't work how you want it to, then you can roll
back the code, or the hiera data, or the classification as needed. You've
got a pretty good expectation that your configuration will return to a
working state (with obvious exceptions). You could even revert to that
config version a year later. But if you depend on agent side functions, you
don't have as strong an expectation because the agent state that might
affect the output of the function isn't versioned with the codebase. It's
effectively an uncontrolled variable.

I'm not trying to discourage you from using agent side functions. In fact,
I'm about to do some work on node_encrypt[1] to make it usable as a
Deferred function and I'm really excited because that means that on Puppet
6, it will no longer be limited to only File types. But I do want you to be
aware of what you're trading it for so you can make an informed decision.

The tl;dr is that these concerns essentially boil down to the fact that
your configuration state will no longer be fully represented in the
catalog. So make sure you account for that when evaluating your options.

[1] https://forge.puppet.com/binford2k/node_encrypt

On Fri, Aug 31, 2018 at 10:42 AM Henrik Lindberg 
wrote:

> On 2018-08-31 13:33, bert hajee wrote:
> > Lindsy,
> >
> > Is it just ment for this use case? I can think of other situations where
> > in might be vary valuable to fetch a value at run-time on the agent. Now
> > whenever we have to get the current state, we need to make a fact. If we
> > can make deferred functions for that that would make things much more
> > simple. I'm not sure if it the still is "The Puppet way". Like to hear
> > any thoughts on that.
> >
> > Bert
> >
>
> Consider a cached catalog - with Deferred values that cached catalog can
> stay the same for as long as it is only the deferred values that need to
> change (and that they can be obtained locally or from service).
>
> Without use of cached catalog, Deferred values are good for things
> that must or are much better suited to be computed fresh on the agent.
>
> - henrik
>
> > On Friday, 31 August 2018 02:11:52 UTC+2, Lindsey Smith wrote:
> >
> > Hi all,
> >
> > We wanted to let you know about an upcoming capability, the Deferred
> > type, that is now present in Puppet 6 nightlies and will be part of
> > the Puppet 6.0 release.
> >
> > A longstanding request has been to allow agents to fetch data for
> > themselves at catalog application time. One key use case for this is
> > getting secrets directly from a store like Conjur, Vault or Consul.
> > Without this capability the master has to be in the middle and
> > secret values are passed in catalogs around more than is necessary.
> >
> > The solution in Puppet 6 is the Deferred type. A Deferred value
> > describes a function call to be made in the future and when placing
> > it in a catalog the agent will replace it with the result of calling
> > the wrapped function before it continues with application as normal.
> >
> > Of course, for the agent to actually fetch data from a keystore the
> > function has to exist on the agent side and be loaded during a run.
> > In Puppet 6.0, these functions will be downloaded from the master
> > via pluginsync from the lib/puppet/functionsdirectory in modules,
> > then loaded during an agent run. Though Deferred is intended
> > primarily for agents running with a master, it does work in the same
> > way with an agent only.
> >
> > https://gist.github.com/turbodog/06d3fecef403bfefd9c8174ede4d9174
> >  >has
> > more explanation and walks you through a simple Deferred function
> > example. Work on this is tracked in PUP-8711
> > and updating the
> > Puppet specification for Deferred is a work in progress happening
> > here: https://github.com/puppetlabs/puppet-specifications/pull/122
> > 
> >
> > If you 

Re: [Puppet Users] Puppet Apache Module

[Ben Ford]

Totally a fair point, thanks for the feedback!

On Fri, Aug 24, 2018 at 8:57 AM Tim Skirvin  wrote:

> Ben Ford  writes:
>
> [puppetlabs/apache is dropping support for RHEL6 and family]
> > Is there a reason you can't pin to the module to a version that supports
> > your needs?
>
> We probably will do so for the duration of the transition.  But
> frankly my management is already pretty frustrated with this module in
> particular due to its complexity, and this will push them over the edge.
> My larger argument is probably "please don't make it more difficult to
> justify your product to my management".
>
> Note that the primary maintainers of Scientific Linux are my
> colleagues.
>
> - Tim Skirvin (tskir...@fnal.gov)
> --
> HPC Systems Administrator / Developer
> http://www.linkedin.com/in/tskirvin
>USCMS-T1 Collaboration Fermilab ECF
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L5dr4Q-s%3DN8YtWRWnVS_98GgxBqyFjxfKk_nJNyFo%3DwiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Apache Module

[Ben Ford]

Is there a reason you can't pin to the module to a version that supports
your needs?

Any users that use either Apache 2.2 or use one of the above operating
> systems should pin to an older version of the module. We will continue to
> support these operating systems for older versions of the module.


On Thu, Aug 23, 2018 at 12:01 PM Tim Skirvin  wrote:

> Davin Hanlon  writes:
>
> > Quick note to let you know of some major work that we're performing
> > to the module. As you probably know, Apache 2.2 has been end-of-lifed
> > since the start of 2018 [...] Therefore, we're taking steps to remove
> > support for that version of Apache from the module. This also impacts
> > the operating systems that we will support for the module. The following
> > operating systems won't be supported by the Apache module after the
> > changes:
>
> >- RHEL 5
> >- RHEL 6
> >- CentOS 5
> >- CentOS 6
> >- Oracle Linux 6
> >- Scientific Linux 6
>
> Is there any chance you'd consider delaying this change?  RHEL 6
> and family are "officially supported" releases for years to come, and I
> and many other sites still use it for many or most most of our services.
> Without speaking for anybody else, if you drop support for Apache 2.2 at
> this point, I'll probably have to transition away from using the
> puppetlabs/apache module entirely, and I'd really rather not.
>
> - Tim Skirvin (tskir...@fnal.gov)
> --
> HPC Systems Administrator / Developer
> http://www.linkedin.com/in/tskirvin
>USCMS-T1 Collaboration Fermilab ECF
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/20180823190134.GB91021%40fnal.gov
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4HKCZwNfrEhh1z0n84i%2B%3Df0cC3RdPErDZeQYEsdo%2B_ig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Automatic parameter lookup including metaparameters

[Ben Ford]

Hi Michael. Can you share the code you tried and the errors you ran into?

On Thu, Aug 9, 2018 at 11:30 AM Michael Watters  wrote:

> Hello,
>
> Is it possible to define metaparameters for a resource in Hiera?  For
> example, I have a class that is currently declared within another class as
> follows.
>
> if !defined(Class['autofs']) {
> class { 'autofs':
> require => [
> Class['authconfig'],
> Class['nfs::client'],
> ],
> }
> }
>
> I would like to get rid of this mess and use a standard include statement
> with parameters defined in my common.yaml as follows.
>
> include 'autofs'
>
> ---
> autofs::require:
> - "Class['authconfig']"
> - "Class['nfs::client']"
>
>
> Will this work or do I have to stick with resource-like declarations to
> define dependencies?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/ea13260d-673f-4322-a787-271c7f4b1259%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4GrkKS%2BwQtaE4hcAq%3DqjmYtiFVr_mh9Bj22vmENH2brg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] is_numeric

[Ben Ford]

First off, you should use data types with your class and then you won't
have to check--the compile won't even succeed unless you've got the right
data type.

class foo (
Integer $subsetting,
) {
# $subsetting is guaranteed to be numeric here

}

Second, you can use the is_a
 function, or the ~=
equality matcher.



On Mon, Aug 6, 2018 at 8:28 AM Helmut Schneider  wrote:

> Hi,
>
> I want to check if a variable is numeric. The manpage says is_numeric
> is deprectaed and I shall user validate_legacy. But
>
> <% if validate_legacy(Numeric, 'validate_numeric', $subsetting) { -%>
>
> Error: Could not retrieve catalog from remote server: Error 500 on
> SERVER: Server Error: Evaluation Error: Error while evaluating a
> Function Call, validate_legacy(validate_numeric) expects a Numeric
> value, got String at
> /etc/puppetlabs/code/modules/bacula/templates/etc/bacula/bacula-dir.conf
> .epp:25:7 on node bsdhelmut1164
>
> What is the proper way to check if something is numeric?
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/xn0lddxg1g5gp4001%40news.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L6GCpzAVt-74-mE%2BXmrLu49_Y8XxOVW4CuXLaDYkxpNsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Check existence of a hierarchy

[Ben Ford]

What you're looking for is the dig() function.
https://puppet.com/docs/puppet/latest/function.html#dig

$profiles.dig('vpn', 'openvpn', 'instances', 'client')

On Wed, Jul 11, 2018 at 8:32 AM Helmut Schneider  wrote:

> Hello all,
>
> let's assume the following structure in a yaml:
>
> profiles:
>   vpn:
> openvpn:
>   instances:
> client:
>   myclient:
> remote:   'openvpn_host 1194'
>
> I would now like to check if e.g. "client" exists:
>
> if ($profiles['vpn']['openvpn']['instances']['client'])
>
> This works as long as the structure
>
> profiles:
>   vpn:
> openvpn:
>   instances:
>
> exists and fails if not (because OpenVPN should not be available for
> that client):
>
> Error: Could not retrieve catalog from remote server: Error 500 on
> SERVER: Server Error: Evaluation Error: Operator '[]' is not applicable
> to an Undef Value. at
> /etc/puppetlabs/code/modules/openvpn/manifests/init.pp:17:7 on node
> my_client
>
> Is there a way to check the existence of a hierarchy without creating
> an empty hierarchy or doing something like
>
>   if is_hash($profiles) {
> if has_key($profiles, 'vpn') {
>   if has_key($profiles['vpn'], 'openvpn') {
> if has_key($profiles['vpn']['openvpn'], 'instances') {
>   ...and so on
> }
>   }
> }
>   }
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails 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/xn0lcc078szqyl1000%40news.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L40ZvgSM-AYJ7HBq_u%2B7MuBYL6GbfEE%3Di9qVn9f5Cu4rQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Introducing new Cisco IOS module for agentless device management

[Ben Ford]

Puppet has launched the agentless Cisco IOS module for Network Devices that
can be downloaded from the Puppet Forge
. This module gives
networking teams an easy way to manage Cisco Catalyst Switches with Puppet
without the need to install an agent on the devices.

This improvement of Puppet agentless approach is another step in the
direction of expanding the type of resources that can be managed with
Puppet, offering Operations and Network teams the option to standardize on
one tool.

Cisco IOS Catalyst module use cases:

   - Extend the use of Puppet to network and legacy devices, like Cisco
   switches, without the need to install an agent on the device;
   - Scale automation across various Cisco network devices to reduce time
   management, downtime, and configuration errors of a manual approach;
   - Ensure switches configurations remain in the desired state at all
   times without having to worry about drift or unauthorized changes that lead
   to errors and downtime.

The module requires the Resource API which can be downloaded from the
Puppet Forge . The Cisco
IOS module uses the agentless Puppet Device, which acts as a proxy node to
request certificates, collect facts, retrieve and apply catalogs and store
reports. The ReadMe for the module provides sample manifests for retrieving
existing configuration data and setting new configuration data.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4DvHCN0zU6WBFJPvk-suPFrmDdftfvh2o%2BB%3DZPN%3DOcvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] New products to help you scale automation success

[Ben Ford]

Whether you’re just starting your automation journey or you’ve been at it a
while, you know that making automation pervasive across your enterprise is
hard.

Three key challenges stand in the way of scaling success:

* It’s hard to know what you have
* It’s hard to scale automation broadly and deeply
* Dev and Ops teams are still siloed

The latest offerings in our product portfolio help you scale your success
with automated discovery, management and delivery of all of your
applications and the infrastructure they run on.


Know What You Have with Puppet Discovery. Puppet Discovery is the most
powerful discovery tool available on the market. Its intuitive dashboard
shows you everything you have running on your servers, VMs, and containers,
on premises or in the cloud. You get deep insights into your infrastructure
so you know what to automate and take action on in order to bring all of
your infrastructure under management.

>> Learn more



Bridge Dev and Ops With All New Continuous Delivery for Puppet
Enterprise. We’re thrilled to introduce a new offering based on the same
CI/CD technology that powers Puppet Pipelines. Continuous Delivery for
Puppet Enterprise unifies Dev and Ops workflows by making continuous
integration and delivery simple for infrastructure managed with Puppet
Enterprise. This product is available to existing customers in June.

>> Learn more



Scale Automation Broadly and Deeply With Puppet Enterprise®. Puppet
Enterprise 2018.1(LTS) includes more ways to help customers scale
automation broadly and deeply with enterprise-grade security and support.

Puppet Tasks™ enhancements: In Puppet Enterprise, new per-node role-based
access control (RBAC) lets you control who can run specific tasks across
groups of nodes. In Puppet Bolt™, our open source task runner, we’ve added
the ability to run task plans on Puppet Enterprise nodes using our
ultra-scalable Puppet orchestrator, which allows you to run tasks across
hundreds of thousands of nodes. Bolt task plans give you the ability to
execute ordered actions as part of a deployment workflow and now, you can
track the execution of those plans directly in the Puppet Enterprise
console. Learn about free Tasks training.

Puppet Development Kit (PDK) support: Puppet Enterprise customers can now
use the PDK to quickly develop and test Puppet code with support when they
need it.

New backup and recovery capabilities: Puppet Enterprise has long been a
core part of disaster recovery planning, making it straightforward to
reproduce business-critical infrastructure in the event of catastrophe.
Now, it’s even easier to incorporate Puppet Enterprise into those plans
with built-in tools to backup and restore the deployment. Combined with its
high-availability features, Puppet Enterprise is always ready if there’s a
problem anywhere in the datacenter or the cloud.

>> Learn more


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L79RmUGNUxBK72%2BXOuj%3DvrHBF8sA%3DZE1Ui9tJ38wT5X%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Hack!

[Ben Ford]

Has Puppet made your life easier like it's made my life easier? Come hang
out on Dec. 7 with other community members, Vox Pupuli, and Puppet
employees to hack on awesome Puppet (and related) projects. Let's get to
know each other!

http://pup.pt/hack

#puppethack is a collaborative, relaxed online Puppet community hack day.
It's an opportunity for Puppet community members, Vox Pupuli, and Puppet
employees to tackle interesting or fun Puppet projects, get to know each
other, and collaborate on pull requests.

Would love to see you there!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L4STrk92OT7j7_%2BUAfThgow0L5b1zLt8Vhv7vd94YvWBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PE console missing the PE_REPO class for agent packages

[Ben Ford]

Hey Mike! I suspect that what you see is the result of modifying your 
basemodulepath or overriding your modulepath in an environment.conf file. 
They should be set something like the following:

root@master:~ # puppet master --configprint basemodulepath
/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
root@master:~ # puppet master --configprint modulepath
/etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules

Hope that helps you track it down!


On Monday, January 25, 2016 at 7:45:25 AM UTC-8, mike r wrote:
>
> Hey all, Im running PE 4.1, master is Ubuntu 14, trying to push out an 
> agent for Centos and Ubuntu 12, using the curl -k script
>
> Problem is on my console, PE Masters classes, I dont see any pe_repo:: 
> options to add additional agent installers,
>
>
> the only classes I see are my standard modules, I dont see the out of box 
> pe_ classes.  I noticed that all my pe_ classes were marked for deletion 
> for some reason. Not sure how to set it back so it shows pe_rep:: and other 
> classes.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails 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/8aedf698-1d49-4b3f-a5a7-b755eaed9da6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Certification Testing discount

[Ben Ford]

To make it easier to get more of you certified, we are offering all Puppet
users an automatic 50 percent discount on any Puppet certification,
reducing the exam fee to $100 through August 31, 2014.

Puppet certifications are available in two areas:

   - *Puppet Professional*: This certification validates system
   administrator competencies in using Puppet to manage their infrastructure:
   http://www.puppetlabs.com/services/certification/puppet-professional.
   - *Puppet Developer*: This validates skills and competencies for
   developers using Ruby to extend the functionality of their Puppet
   infrastructure:
   http://www.puppetlabs.com/services/certification/puppet-developer

You can schedule an appointment to take a Puppet certification test at
http://www.pearsonvue.com/puppetlabs/

Get all of the details, including FAQs, step-by-step guides, and more at
http://puppetlabs.com/services/certification

Thanks!

-- 
Ben Ford | Training Solutions Engineer
Puppet Labs, Inc.
926 NW 13th Ave, Suite #210
Portland, OR 97209

509.592.7291
ben.f...@puppetlabs.com

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails 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/CACkW_L68s89R9XHb0w0i05H7H_%3DDwZBaVYvJBn0cqusqhHfthw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announcing our new quest based Learning VM

[Ben Ford]

Hi,

We just rolled out the new and improved Learning VM — now with fun quests to 
learn Puppet at your own pace. If you've been meaning to explore the technology 
in depth, now you can do so with a series of detailed, multi-step quests. The 
Learning VM covers topics such as: accessing the Puppet Enterprise console, 
writing and using Puppet modules, and delving into Puppet resources, manifests, 
facts and more.

Check out the new Learning VM: http://puppetlabs.com/download-learning-vm

Happy learning.

- Ben

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails 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/c43a3c51-cdd0-4ea6-96c7-e38e35352d4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] recursive descent

[Ben Ford]

If you override something in a recursive directory, you're overriding 
everything. The subdirectories are being managed explicitly by the resource 
managing them, not by a combination of it and the parent. Look inline below:

On Tuesday, December 17, 2013 11:12:21 AM UTC-8, Andy Spiegl wrote:

   
 http://christian.hofstaedtler.name/blog/2008/11/puppet-managing-directories-recursively.html
  

 I thought I had understood recursive directory management.  It worked 
 fine until I switched to puppet v3 (Debian 3.3.2-1puppetla to be exact) 
 Since then, files in subdirs aren't copied anymore. 

 An example: 
   File { 
 owner = nagios, 
 group = nagios, 
 mode  = '0644', 
   } 
   file { '/var/lib/nagios': 
 ensure= directory, 
 source= 'puppet:///modules/nagios/var_lib_nagios', 
 recurse   = true, 
   } 



Manages /var/lib/nagios with recurse true.
 

  file { '/var/lib/nagios/plugins': 
 ensure= directory, 
 recurse   = true, 
 mode  = '0775', 
   } 



Completely takes precedence over File['/var/lib/nagios'] and manages 
'/var/lib/nagios/plugins' telling Puppet that all you care about is that 
it's a directory with mode 775. Notice that you no longer have a source for 
this subdirectory, so it's explicitly not managed.

If you add source = 'puppet:///modules/nagios/var_lib_nagios/plugins' then 
I suspect you'll get what you want.

 

   file { '/var/lib/nagios/bin': 
 ensure= directory, 
 recurse   = true, 
 mode  = '0775', 
   } 

  lama:~/.../puppet/modules/nagios ls -la files/var_lib_nagios 
  total 8 
  drwxrwxr-x 2 andy users 4096 2013-11-15 15:56:23 bin/ 
  drwxrwxr-x 2 andy users 4096 2013-11-25 12:01:14 plugins/ 

 Why aren't these directories copied to /var/lib/nagios? 
 I tried setting recurselimit to '2' but that didn't help either. 

 Thanks for any hint! 
  Andy. 


 -- 
  A mathematician is a machine for converting coffee into theorems. 
  (Alfred Renyi) 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails 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/80da2632-5cc6-453f-96f6-c01d1e9b85a1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] recursive descent

[Ben Ford]

   file { '/var/lib/nagios/plugins': 
 ensure= directory, 
 recurse   = true, 
 mode  = '0775', 
   } 


I should also point out that this is unnecessary, as Puppet will 
automatically promote read permissions to read  execute permissions for 
directories. If you simply remove the second file declarations from your 
code, you'll have the behavior that I think you're expecting.

http://docs.puppetlabs.com/references/latest/type.html#file-attribute-mode

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails 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/f4d039a2-d13e-4a98-b9d2-80e9ebea0785%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.