[Puppet Users] forge module metadata: dependencies

[Gabriel Filion]

Hello,

recently, a user of a module I wrote reported a bug with dependencies.
after some discussions on the IRC channel, it turned out that there was
a bug in the 3.x series which is not scheduled to be fixed:

https://tickets.puppetlabs.com/browse/PUP-3121

It seems as though using user-module and user/module both work, and the
latter works around the puppet 3.x issue.

Now I'm wondering if using slashes to split user name from module name
in dependency specifications in the metadata.json file is a thing that
will stick around. or is it planned to be deprecated somewhat soon?

documentation still mentions using slashes is OK

https://docs.puppetlabs.com/puppet/latest/reference/modules_metadata.html#specifying-dependencies

and puppetlabs' modules seem to be doing this too.

it's a bit counterintuitive to specify module name with user-module and
then dependencies with user/module though.

-- 
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/56F22EE6.8080606%40lelutin.ca.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

Thanks Eric.

I know I'm being super irritating on this thread, but a link from one to
the other might make this management proof.

For now, I'll just send along both to those that ask.

Thanks,

Trevor

On Tue, Mar 22, 2016 at 4:54 PM, Eric Sorenson  wrote:

> Oh boy. It could, I guess, it's HTML so anything is possible.  But the
> canonical location for the component versions is on the docs site which is
> its own CMS and it's a lot of data:
>
> https://docs.puppetlabs.com/pe/latest/overview_version_table.html
>
>
>
> On Mar 22, 2016, at 1:50 PM, Trevor Vaughan 
> wrote:
>
> Security releases are really all that's important to most
> compliance-focused orgs.
>
> Could that page link to the versions of each sub-component that is
> included?
>
> Thanks!
>
> Trevor
>
> On Tue, Mar 22, 2016 at 11:37 AM, Eric Sorenson <
> eric.soren...@puppetlabs.com> wrote:
>
>> Sorry for the slow reply, we had some internal ducks to get in a row.
>> The enterprise support page now shows the current support dates for all the
>> recent series:
>>
>> https://puppetlabs.com/misc/puppet-enterprise-lifecycle
>>
>> As a practical matter we're going to provide open-source releases of
>> components of a particular PE series for as long as that PE series is
>> supported; outside of security fixes though, the content of releases behind
>> the current one will be driven largely by customer requests.
>>
>> --eric0
>>
>> On Wednesday, March 16, 2016 at 9:57:05 AM UTC-7, Trevor Vaughan wrote:
>>>
>>> Certainly possible, but deductions aren't stated facts on URLs that you
>>> can put in front of management.
>>>
>>> Trevor
>>>
>>> On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho <
>>> mig...@instruct.com.br> wrote:
>>>
 On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan <
 tvaug...@onyxpoint.com> wrote:
 > Thanks Carthik. Unfortunately, we need to know this for all of the
 > components, FOSS or otherwise.
 >

 I think one can deduce that, if PE 3 series has an EOL set to July 28,
 2016, all FOSS components present there will most definitely not be
 supported anymore also.

 --
 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/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Trevor Vaughan
>>> Vice President, Onyx Point, Inc
>>> (410) 541-6699
>>>
>>> -- This account not approved for unencrypted proprietary information --
>>>
>>
>> --
>> 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/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
>
> -- This account not approved for unencrypted proprietary information --
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/15QSPcvkGDI/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANs%2BFoW04-0UUP4%2BkJCdkFvWky%3DV1E7O9Rqn-8Xt7tw9NTPHVg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
> puppet platform // coffee // techno // bicycles
>
> --
> 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/2877A9CB-6227-4FFF-A66B-3760EA3A45DD%40puppetlabs.com
> 
> .
>
> For more options, visit https://grou

Re: [Puppet Users] Puppet 4 on Debian Jessie amd64

[Melissa Stone]

Hi Friedhelm,

Have you enabled the PC1 repos?

I can't tell what repos you have enabled or where you got the puppetserver
packages you're using, but you'll have to enable the PC1 jessie repo to
access puppet-agent.

https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html has
a lot more information on that.

As a summary, you'll want to run:

wget http://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb ; dpkg
-i puppetlabs-release-pc1-jessie.deb ; apt-get update


You can do a check to make sure you have the puppetlabs PC1 repo enabled by
running `apt-cache policy`. You'll get a bunch of output, but the piece you
want to make sure is there should be:

 500 http://apt.puppetlabs.com/ jessie/PC1 amd64 Packages
 release o=Puppetlabs,a=jessie,n=jessie,l=Puppetlabs,c=PC1
 origin apt.puppetlabs.com

Once you've verified you have the PC1 repo enabled, apt-get install
puppet-agent should just work.

I hope that helps!

On Tue, Mar 22, 2016 at 3:52 PM <4nu...@gmail.com> wrote:

> Hi!
>
> I have the same problem. But puppet-agent is not available.
>
> apt-get -y install puppetserver
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>>  puppetserver : Depends: puppet-agent (>= 1.4.0) but it is not installable
>> E: Unable to correct problems, you have held broken packages.
>>
>> sudo apt-get -y install puppet-agent
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package puppet-agent is not available, but is referred to by another
> package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> *# uname -a*
> Linux puppet 4.1.19+ #858 Tue Mar 15 15:52:03 GMT 2016 armv6l GNU/Linux
>
> *cat /etc/os-release*
> PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="8"
> VERSION="8 (jessie)"
> ID=raspbian
> ID_LIKE=debian
> HOME_URL="http://www.raspbian.org/";
> SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";
>
>
> but here i find packages:
> http://apt.puppetlabs.com/pool/jessie/PC1/p/puppet-agent/
>
> does anybody know why i cant install them?
>
> Cheers,
> Friedhelm
>
> On Monday, July 27, 2015 at 7:17:17 PM UTC+2, Melissa Stone wrote:
>>
>> On Mon, Jul 27, 2015 at 2:43 AM, Richard Wales 
>> wrote:
>> > Hi folks,
>> >
>> > Apparently PC1 is available on Debian Jessie now. Unfortunately, I
>> can't get
>> > it to work. I've attached a vagrant file to facilitate reproduction
>> (remove
>> > the .txt extension that I had to add to upload it).
>> >
>> > Here are the relevant commands I am running (as per the docs at
>> > https://docs.puppetlabs.com/puppet/latest/reference/install_linux.html
>> ):
>> >
>> > # wget https://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb
>> > # dpkg -i puppetlabs-release-pc1-jessie.deb
>> > # apt-get update
>> > # apt-get install puppetserver -y # This fails
>>
>> We have puppet-agent packages available for Debian Jessie, but not
>> Puppet Server packages[1]. Those should be available with the next
>> Puppet Server release. So, you can't yet run Debian Jessie as a
>> master, but you can run it as an agent with the puppet-agent package
>> against a master on a different platform.
>>
>> [1] - http://apt.puppetlabs.com/pool/jessie/PC1/p/
>> >
>> > The bottom line is the new packages aren't available; only the old
>> (puppet
>> > 3.7.x packages). Can anyone shed any light? Where am I going wrong
>> guys?
>> >
>> > Cheers,
>> > Richard
>> >
>> > P.S. Here are some diagnostic commands for the curious:
>> >
>> > # apt-cache search puppet | grep ^puppet
>> >
>> > ==> default: puppet - configuration management system, agent
>> >
>> > ==> default: puppet-common - configuration management system
>> >
>> > ==> default: puppet-el - syntax highlighting for puppet manifests in
>> emacs
>> >
>> > ==> default: puppet-testsuite - configuration management system,
>> development
>> > test suite
>> >
>> > ==> default: puppetmaster - configuration management system, master
>> service
>> >
>> > ==> default: puppetmaster-common - configuration management system,
>> master
>> > common files
>> >
>> > ==> default: puppetmaster-passenger - configuration management system,
>> > scalable master service
>> >
>> > ==> default: puppet-lint - check puppet manifests for style guide
>> conformity
>> >
>> > ==> default: puppet-module-puppetlabs-apache - Puppet module for apache
>> >
>> > ==> default: puppet-module-puppetlabs-apt - Puppet module for apt
>> >
>> > ==> default: puppet-module-puppetlab

Re: [Puppet Users] Puppet 4 on Debian Jessie amd64

[4null4]

Hi!

I have the same problem. But puppet-agent is not available.

apt-get -y install puppetserver
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  puppetserver : Depends: puppet-agent (>= 1.4.0) but it is not installable
> E: Unable to correct problems, you have held broken packages.
>
> sudo apt-get -y install puppet-agent
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package puppet-agent is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

*# uname -a*
Linux puppet 4.1.19+ #858 Tue Mar 15 15:52:03 GMT 2016 armv6l GNU/Linux

*cat /etc/os-release*
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/";
SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";


but here i find 
packages: http://apt.puppetlabs.com/pool/jessie/PC1/p/puppet-agent/

does anybody know why i cant install them?

Cheers, 
Friedhelm

On Monday, July 27, 2015 at 7:17:17 PM UTC+2, Melissa Stone wrote:
>
> On Mon, Jul 27, 2015 at 2:43 AM, Richard Wales  > wrote: 
> > Hi folks, 
> > 
> > Apparently PC1 is available on Debian Jessie now. Unfortunately, I can't 
> get 
> > it to work. I've attached a vagrant file to facilitate reproduction 
> (remove 
> > the .txt extension that I had to add to upload it). 
> > 
> > Here are the relevant commands I am running (as per the docs at 
> > https://docs.puppetlabs.com/puppet/latest/reference/install_linux.html 
> ): 
> > 
> > # wget https://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb 
> > # dpkg -i puppetlabs-release-pc1-jessie.deb 
> > # apt-get update 
> > # apt-get install puppetserver -y # This fails 
>
> We have puppet-agent packages available for Debian Jessie, but not 
> Puppet Server packages[1]. Those should be available with the next 
> Puppet Server release. So, you can't yet run Debian Jessie as a 
> master, but you can run it as an agent with the puppet-agent package 
> against a master on a different platform. 
>
> [1] - http://apt.puppetlabs.com/pool/jessie/PC1/p/ 
> > 
> > The bottom line is the new packages aren't available; only the old 
> (puppet 
> > 3.7.x packages). Can anyone shed any light? Where am I going wrong guys? 
> > 
> > Cheers, 
> > Richard 
> > 
> > P.S. Here are some diagnostic commands for the curious: 
> > 
> > # apt-cache search puppet | grep ^puppet 
> > 
> > ==> default: puppet - configuration management system, agent 
> > 
> > ==> default: puppet-common - configuration management system 
> > 
> > ==> default: puppet-el - syntax highlighting for puppet manifests in 
> emacs 
> > 
> > ==> default: puppet-testsuite - configuration management system, 
> development 
> > test suite 
> > 
> > ==> default: puppetmaster - configuration management system, master 
> service 
> > 
> > ==> default: puppetmaster-common - configuration management system, 
> master 
> > common files 
> > 
> > ==> default: puppetmaster-passenger - configuration management system, 
> > scalable master service 
> > 
> > ==> default: puppet-lint - check puppet manifests for style guide 
> conformity 
> > 
> > ==> default: puppet-module-puppetlabs-apache - Puppet module for apache 
> > 
> > ==> default: puppet-module-puppetlabs-apt - Puppet module for apt 
> > 
> > ==> default: puppet-module-puppetlabs-concat - Puppet module for concat 
> > 
> > ==> default: puppet-module-puppetlabs-firewall - Puppet module for 
> Firewall 
> > management 
> > 
> > ==> default: puppet-module-puppetlabs-inifile - Puppet module for ini 
> files 
> > 
> > ==> default: puppet-module-puppetlabs-mysql - Puppet module for mysql 
> > 
> > ==> default: puppet-module-puppetlabs-ntp - Puppet module for ntp 
> > 
> > ==> default: puppet-module-puppetlabs-postgresql - Puppet module for 
> > PostgreSQL database 
> > 
> > ==> default: puppet-module-puppetlabs-stdlib - Puppet module standard 
> > library 
> > 
> > ==> default: puppet-module-puppetlabs-xinetd - Puppet module for xinetd 
> > 
> > ==> default: puppet-module-saz-memcached - Puppet module for memcached 
> > 
> > ==> default: puppetlabs-release-pc1 - Release packages for the Puppet 
> Labs 
> > PC1 repository 
> > 
> > ==> default: puppet-agent - The Puppet Agent package contains all of the 
> > elements needed to run puppet, including ruby, facter, hiera and 
> > mcollective. 
> > 
> > 
> > # uname -a 
> > 
> > ==> default: Linux te

Re: [Puppet Users] look up hiera hash's subkey within yaml

[Brett Swift]

Well that's what I've been going off, but I haven't figured out the right 
syntax. 

I've tried escaping the nested single quotes.. no luck. 

One strange thing right now is I can't even interpolate facts.

---
test: "%{::hostname}" 

 is failing on a lookup.  hmm. 



On Tuesday, 22 March 2016 16:00:12 UTC-6, Carthik Sharma wrote:
>
> This might help:
>
> https://docs.puppetlabs.com/hiera/3.1/variables.html#interpolating-hash-or-array-elements
>
> Thanks.
>
> On Tue, Mar 22, 2016 at 2:14 PM, Brett Swift  > wrote:
>
>> This is a bit nutty, but hopefully there's a way to do this.
>>
>> So far I have only been able to get the parent hash, not the nested one. 
>>   
>>
>> The reason I don't want to do this in a manifest,  is because I'd like to 
>> use pieces of this hash within hiera itself.
>>
>> This gist is what I'm trying to do: 
>> https://gist.github.com/brettswift/560af53d379e0d86730c
>>
>> pasted here: 
>> group_allocation:
>> devcoreoeml030.matrix.sjrb.ad: smokestack
>> devcorebrml030.matrix.sjrb.ad: smokestack
>> devcoreesbl030.matrix.sjrb.ad: smokestack
>> devcoreoeml091.matrix.sjrb.ad: the091
>> devcorebrml091.matrix.sjrb.ad: the091
>> devcoreesbl091.matrix.sjrb.ad: the091
>> devcorepptl003.matrix.sjrb.ad: dev_master
>> tstcorepptl003.matrix.sjrb.ad: tst_master
>> devcorepptl918.matrix.sjrb.ad: brett_sandbox
>> devcorepptl919.matrix.sjrb.ad: brett_sandbox
>> groups:
>> core030:
>> data:
>> tag: smokestack
>> owner: bcornies
>> the091:
>> data:
>> tag: brettstack
>> owner: bswift
>> brett_sandbox:
>> data:
>> tag: brett
>> owner: bswift
>> my_group_name: "%{hiera('group_allocation')}.%{::fqdn}"
>> my_group: "%{hiera('groups[%{hiera('my_group_name')}]')}"
>> #my_tag: ... 
>>
>>
>> My goal is to find access to the tag, owner, etc.   This is a bit nutty 
>> as it's kind of relational data in hieradata, but we're hoping we can do 
>> this.
>>
>> Right now the two lookups at the bottom do not work.   I can get the top 
>> level lookup, but beyond that - it's not working.  Has someone done this? I 
>> can only seem to find examples to compare with this being done in a 
>> manifest file, not in a yaml 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/0695140c-1d59-4708-9e35-f6020bcf3345%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/4d1587ff-0e5c-4a05-8614-81ad08d07729%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] look up hiera hash's subkey within yaml

[Carthik Sharma]

This might help:
https://docs.puppetlabs.com/hiera/3.1/variables.html#interpolating-hash-or-array-elements

Thanks.

On Tue, Mar 22, 2016 at 2:14 PM, Brett Swift  wrote:

> This is a bit nutty, but hopefully there's a way to do this.
>
> So far I have only been able to get the parent hash, not the nested one.
>
> The reason I don't want to do this in a manifest,  is because I'd like to
> use pieces of this hash within hiera itself.
>
> This gist is what I'm trying to do:
> https://gist.github.com/brettswift/560af53d379e0d86730c
>
> pasted here:
> group_allocation:
> devcoreoeml030.matrix.sjrb.ad: smokestack
> devcorebrml030.matrix.sjrb.ad: smokestack
> devcoreesbl030.matrix.sjrb.ad: smokestack
> devcoreoeml091.matrix.sjrb.ad: the091
> devcorebrml091.matrix.sjrb.ad: the091
> devcoreesbl091.matrix.sjrb.ad: the091
> devcorepptl003.matrix.sjrb.ad: dev_master
> tstcorepptl003.matrix.sjrb.ad: tst_master
> devcorepptl918.matrix.sjrb.ad: brett_sandbox
> devcorepptl919.matrix.sjrb.ad: brett_sandbox
> groups:
> core030:
> data:
> tag: smokestack
> owner: bcornies
> the091:
> data:
> tag: brettstack
> owner: bswift
> brett_sandbox:
> data:
> tag: brett
> owner: bswift
> my_group_name: "%{hiera('group_allocation')}.%{::fqdn}"
> my_group: "%{hiera('groups[%{hiera('my_group_name')}]')}"
> #my_tag: ...
>
>
> My goal is to find access to the tag, owner, etc.   This is a bit nutty as
> it's kind of relational data in hieradata, but we're hoping we can do this.
>
> Right now the two lookups at the bottom do not work.   I can get the top
> level lookup, but beyond that - it's not working.  Has someone done this? I
> can only seem to find examples to compare with this being done in a
> manifest file, not in a yaml 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/0695140c-1d59-4708-9e35-f6020bcf3345%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/CAOzFSfFw2CmHaY1CT%3D6oJ%3DqmV3ZTD9FoYG2AZnBRuH6CHYooTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Please Confirm: Puppet Directory Environments can not be named "master" ?

[Carthik Sharma]

To answer the question in the subject, you're correct, as documented here
for Puppet 3.8

https://docs.puppetlabs.com/puppet/3.8/reference/environments_classic.html#allowed-names



On Tue, Mar 22, 2016 at 1:41 AM, 'Robert Heinzmann' via Puppet Users <
puppet-users@googlegroups.com> wrote:

> Hello,
>
> I'm using PuppetServer 1.1.3 and want to use directory environments (I can
> not update to puppet 4 because of
> http://projects.theforeman.org/issues/8447, Foreman is used for reporting
> and facts only (CMDB like)).
>
> The main puppet repo has 2 branches:
>
>- master (production)
>- development (test&dev)
>
> I use r10k to manage the environments under /etc/puppet/environments
>
> --- o<
> :sources:
>   example:
> basedir: /etc/puppet/environments
> prefix: false
> remote: 
> --- o<
>
> The following master setup has worked for both "master" and "development"
>
>  o<  
> # file /etc/puppet/puppet.conf
> [master]
>
> # insecure not via server_facts ...
> environment = ...
> # PuppetDB Enabled
> storeconfigs = true
> storeconfigs_backend = ...
> reports = ...
>
> # Hiera Config File
> hiera_config = ...
> default_manifest =
> /etc/puppet/environments/$environment/manifests/site.pp
> manifestdir = /etc/puppet/environments/$environment/manifests
> manifest = /etc/puppet/environments/$environment/manifests/site.pp
> modulepath =
> /etc/puppet/modules:/etc/puppet/environments/$environment/modules:/etc/puppet/environments/$environment/forge:/etc/puppet/environments/$environment/3rdparty
> # ENC Enabled
> node_terminus = exec
> external_nodes = ...
> ## see
> https://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#serverfacts-variable
> trusted_server_facts = true
> trusted_node_data = true
> ## Make sure master uses another directory so master can be agent of
> someone else
> ssldir = ...
> certname = ...
> server = ...
>
> ## Add extra DNS Names
> dns_alt_names = ...
>  o<  
>
> Now I want to switch to directory environments changed configuration as
> follows:
>
> Puppet master config is as follows:
>
>  o<  
> # file /etc/puppet/puppet.conf
> [master]
>
> environment = ...
> # PuppetDB Enabled
> storeconfigs = true
> storeconfigs_backend = ...
> reports = ...
>
> # Hiera Config File
> hiera_config = ...
> ## Directory Environments enabled
> default_manifest = /etc/puppet/manifests/site.pp
> environmentpath = /etc/puppet/environments
> environment_timeout = 0
> basemodulepath = /etc/puppet/modules
> disable_per_environment_manifest = false
> # ENC Enabled
> node_terminus = exec
> external_nodes = ...
> ## see
> https://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#serverfacts-variable
> trusted_server_facts = true
> trusted_node_data = true
> ## Make sure master uses another directory so master can be agent of
> someone else
> ssldir = ...
> certname = ...
> server = ...
>
> ## Add extra DNS Names
> dns_alt_names = ...
>  o<  
>
> The environment.conf is
>
>  o<  
> # file /etc/puppet/environments/master/environment.conf and
> # file /etc/puppet/environments/development/environment.conf
> ## See
> https://docs.puppetlabs.com/puppet/latest/reference/config_file_environment.html
>
> # The module path
> modulepath = ./modules/:./forge/:./3rdparty/:$basemodulepath
>
> # Manifest
> manifest = manifests/site.pp
>
> # current or future (3.8 only)
> # parser = current
>
> ## Path to custom script
> # config_version=
>
> ## Timeout for cache
> environment_timeout = unlimited
>  o<  
>
> This setup works for environment "development" but not "master".
>
>
>> *agent shell# puppet agent --onetime --test --environment master => Fail
>> with 404Error: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: Could not find class my_webserver for webserver-test1 on node
>> webserver-test1*
>
>
> *agent shell# puppet agent --onetime --test --environment development =>
>> OK*
>
>
> If I do "mv /etc/puppet/environments/master
> /etc/puppet/environments/mytest123" and restart the puppetserver mytest123
> environment works
>
> *agent shell# puppet agent --onetime --test --environment mytest123 => OK*
>
>
> If I do "mv /etc/puppet/environments/mytest123
> /etc/puppet/environments/master" and restart the puppetserver master
> environment FAILES again
>
>
>> *agent shell# puppet agent --onetime --test --environment master => Fail
>> with 404Error: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: Could not find class my_webserver for webserver-test1 on node
>> webserver-test1*
>
>
> So it is not the repo content but the name of the environment causing the
> problem I guess.
>
> Has someone seen this issue yet ??
>
> Using "prefix: true" on r10k should fix the issue and gene

[Puppet Users] look up hiera hash's subkey within yaml

[Brett Swift]

This is a bit nutty, but hopefully there's a way to do this.

So far I have only been able to get the parent hash, not the nested one.   

The reason I don't want to do this in a manifest,  is because I'd like to 
use pieces of this hash within hiera itself.

This gist is what I'm trying to do: 
https://gist.github.com/brettswift/560af53d379e0d86730c

pasted here: 
group_allocation:
devcoreoeml030.matrix.sjrb.ad: smokestack
devcorebrml030.matrix.sjrb.ad: smokestack
devcoreesbl030.matrix.sjrb.ad: smokestack
devcoreoeml091.matrix.sjrb.ad: the091
devcorebrml091.matrix.sjrb.ad: the091
devcoreesbl091.matrix.sjrb.ad: the091
devcorepptl003.matrix.sjrb.ad: dev_master
tstcorepptl003.matrix.sjrb.ad: tst_master
devcorepptl918.matrix.sjrb.ad: brett_sandbox
devcorepptl919.matrix.sjrb.ad: brett_sandbox
groups:
core030:
data:
tag: smokestack
owner: bcornies
the091:
data:
tag: brettstack
owner: bswift
brett_sandbox:
data:
tag: brett
owner: bswift
my_group_name: "%{hiera('group_allocation')}.%{::fqdn}"
my_group: "%{hiera('groups[%{hiera('my_group_name')}]')}"
#my_tag: ... 


My goal is to find access to the tag, owner, etc.   This is a bit nutty as 
it's kind of relational data in hieradata, but we're hoping we can do this.

Right now the two lookups at the bottom do not work.   I can get the top 
level lookup, but beyond that - it's not working.  Has someone done this? I 
can only seem to find examples to compare with this being done in a 
manifest file, not in a yaml 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/0695140c-1d59-4708-9e35-f6020bcf3345%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Eric Sorenson]

Oh boy. It could, I guess, it's HTML so anything is possible.  But the 
canonical location for the component versions is on the docs site which is its 
own CMS and it's a lot of data:

https://docs.puppetlabs.com/pe/latest/overview_version_table.html



On Mar 22, 2016, at 1:50 PM, Trevor Vaughan  wrote:

> Security releases are really all that's important to most compliance-focused 
> orgs.
> 
> Could that page link to the versions of each sub-component that is included?
> 
> Thanks!
> 
> Trevor
> 
> On Tue, Mar 22, 2016 at 11:37 AM, Eric Sorenson  > wrote:
> Sorry for the slow reply, we had some internal ducks to get in a row.  The 
> enterprise support page now shows the current support dates for all the 
> recent series:
> 
> https://puppetlabs.com/misc/puppet-enterprise-lifecycle 
> 
> 
> As a practical matter we're going to provide open-source releases of 
> components of a particular PE series for as long as that PE series is 
> supported; outside of security fixes though, the content of releases behind 
> the current one will be driven largely by customer requests. 
> 
> --eric0
> 
> On Wednesday, March 16, 2016 at 9:57:05 AM UTC-7, Trevor Vaughan wrote:
> Certainly possible, but deductions aren't stated facts on URLs that you can 
> put in front of management.
> 
> Trevor
> 
> On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho 
> mailto:mig...@instruct.com.br>> wrote:
> On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan  > wrote:
> > Thanks Carthik. Unfortunately, we need to know this for all of the
> > components, FOSS or otherwise.
> >
> 
> I think one can deduce that, if PE 3 series has an EOL set to July 28,
> 2016, all FOSS components present there will most definitely not be
> supported anymore also.
> 
> --
> 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/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> 
> -- 
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699 
> 
> -- This account not approved for unencrypted proprietary information --
> 
> -- 
> 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/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com
>  
> .
> 
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> 
> -- 
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
> 
> -- This account not approved for unencrypted proprietary information --
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Puppet Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/puppet-users/15QSPcvkGDI/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/CANs%2BFoW04-0UUP4%2BkJCdkFvWky%3DV1E7O9Rqn-8Xt7tw9NTPHVg%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

Eric Sorenson - eric.soren...@puppetlabs.com 
 - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

-- 
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/2877A9CB-6227-4

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

Security releases are really all that's important to most
compliance-focused orgs.

Could that page link to the versions of each sub-component that is included?

Thanks!

Trevor

On Tue, Mar 22, 2016 at 11:37 AM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:

> Sorry for the slow reply, we had some internal ducks to get in a row.  The
> enterprise support page now shows the current support dates for all the
> recent series:
>
> https://puppetlabs.com/misc/puppet-enterprise-lifecycle
>
> As a practical matter we're going to provide open-source releases of
> components of a particular PE series for as long as that PE series is
> supported; outside of security fixes though, the content of releases behind
> the current one will be driven largely by customer requests.
>
> --eric0
>
> On Wednesday, March 16, 2016 at 9:57:05 AM UTC-7, Trevor Vaughan wrote:
>>
>> Certainly possible, but deductions aren't stated facts on URLs that you
>> can put in front of management.
>>
>> Trevor
>>
>> On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho <
>> mig...@instruct.com.br> wrote:
>>
>>> On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan 
>>> wrote:
>>> > Thanks Carthik. Unfortunately, we need to know this for all of the
>>> > components, FOSS or otherwise.
>>> >
>>>
>>> I think one can deduce that, if PE 3 series has an EOL set to July 28,
>>> 2016, all FOSS components present there will most definitely not be
>>> supported anymore also.
>>>
>>> --
>>> 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/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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/CANs%2BFoW04-0UUP4%2BkJCdkFvWky%3DV1E7O9Rqn-8Xt7tw9NTPHVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Options for notifying external services in case of changing exported resources.

[Jelle Smet]

>
>
> If that's your only alternative, and -- as we've already covered -- you 
> must not use triggers, then you are out of luck.  Puppet does not emit any 
> notifications when exported resource data change.  On the other hand, it 
> does emit notifications when resource changes are applied to a node, 
> whatever the type and origin of the resource.  Changes to exported resource 
> data are associated with applying resource changes, but the two are not 
> directly coupled.
>
>
Understood thanks for the clarification. This has been very helpful.

Much appreciated all the effort!

- Jelle

-- 
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/f04ce0eb-dad7-4f81-a581-340da69c784a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Options for notifying external services in case of changing exported resources.

[Jelle Smet]

>
> (like stuff needing guy/rest-api to update config).. I'd still make puppet 
> write config files.. perhaps in json format - and then simply catch puppet 
> return code in script running puppet on the "config server that pulls the 
> exported resources".. and post those new json files (filestamp tells it 
> like it is ;) - to the config endpoint.
>

yeah i see your point.

Tnx for the feedback
 

-- 
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/7cc84af8-0a0c-489f-9855-44c1d857a5c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Eric Sorenson]

Sorry for the slow reply, we had some internal ducks to get in a row.  The 
enterprise support page now shows the current support dates for all the 
recent series:

https://puppetlabs.com/misc/puppet-enterprise-lifecycle

As a practical matter we're going to provide open-source releases of 
components of a particular PE series for as long as that PE series is 
supported; outside of security fixes though, the content of releases behind 
the current one will be driven largely by customer requests. 

--eric0

On Wednesday, March 16, 2016 at 9:57:05 AM UTC-7, Trevor Vaughan wrote:
>
> Certainly possible, but deductions aren't stated facts on URLs that you 
> can put in front of management.
>
> Trevor
>
> On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho <
> mig...@instruct.com.br> wrote:
>
>> On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan  
>> wrote:
>> > Thanks Carthik. Unfortunately, we need to know this for all of the
>> > components, FOSS or otherwise.
>> >
>>
>> I think one can deduce that, if PE 3 series has an EOL set to July 28,
>> 2016, all FOSS components present there will most definitely not be
>> supported anymore also.
>>
>> --
>> 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/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
>
> -- This account not approved for unencrypted proprietary information --
>

-- 
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/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Options for notifying external services in case of changing exported resources.

[Klavs Klavsen]

I configure monitoring by letting puppet create exported resources on all 
hosts (where my rules then figure out what to monitor).. and then I simply 
pull those resources on the monitor servers - which results in config files 
for the things to monitor. Works beautifully with nagios/icinga and other 
text-based configs.

if I were to interface with something stupid (like stuff needing 
guy/rest-api to update config).. I'd still make puppet write config files.. 
perhaps in json format - and then simply catch puppet return code in script 
running puppet on the "config server that pulls the exported resources".. 
and post those new json files (filestamp tells it like it is ;) - to the 
config endpoint.

-- 
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/24d44f87-f960-414d-89f4-cdaef2dd52d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Please Confirm: Puppet Directory Environments can not be named "master" ?

['Robert Heinzmann' via Puppet Users]

Hello, 

I'm using PuppetServer 1.1.3 and want to use directory environments (I can 
not update to puppet 4 because of 
http://projects.theforeman.org/issues/8447, Foreman is used for reporting 
and facts only (CMDB like)).

The main puppet repo has 2 branches: 

   - master (production)
   - development (test&dev)

I use r10k to manage the environments under /etc/puppet/environments

--- o<
:sources:
  example:
basedir: /etc/puppet/environments
prefix: false
remote: 
--- o<

The following master setup has worked for both "master" and "development"

 o<  
# file /etc/puppet/puppet.conf 
[master]

# insecure not via server_facts ...
environment = ...
# PuppetDB Enabled
storeconfigs = true
storeconfigs_backend = ...
reports = ...

# Hiera Config File
hiera_config = ...
default_manifest = 
/etc/puppet/environments/$environment/manifests/site.pp
manifestdir = /etc/puppet/environments/$environment/manifests
manifest = /etc/puppet/environments/$environment/manifests/site.pp
modulepath = 
/etc/puppet/modules:/etc/puppet/environments/$environment/modules:/etc/puppet/environments/$environment/forge:/etc/puppet/environments/$environment/3rdparty
# ENC Enabled
node_terminus = exec
external_nodes = ...
## see 
https://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#serverfacts-variable
trusted_server_facts = true
trusted_node_data = true
## Make sure master uses another directory so master can be agent of 
someone else
ssldir = ...
certname = ...
server = ...

## Add extra DNS Names
dns_alt_names = ...
 o<  

Now I want to switch to directory environments changed configuration as 
follows:

Puppet master config is as follows: 

 o<  
# file /etc/puppet/puppet.conf 
[master]

environment = ...
# PuppetDB Enabled
storeconfigs = true
storeconfigs_backend = ...
reports = ...

# Hiera Config File
hiera_config = ...
## Directory Environments enabled
default_manifest = /etc/puppet/manifests/site.pp
environmentpath = /etc/puppet/environments
environment_timeout = 0
basemodulepath = /etc/puppet/modules
disable_per_environment_manifest = false
# ENC Enabled
node_terminus = exec
external_nodes = ...
## see 
https://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#serverfacts-variable
trusted_server_facts = true
trusted_node_data = true
## Make sure master uses another directory so master can be agent of 
someone else
ssldir = ...
certname = ...
server = ...

## Add extra DNS Names
dns_alt_names = ...
 o<  

The environment.conf is 

 o<  
# file /etc/puppet/environments/master/environment.conf and
# file /etc/puppet/environments/development/environment.conf
## See 
https://docs.puppetlabs.com/puppet/latest/reference/config_file_environment.html

# The module path
modulepath = ./modules/:./forge/:./3rdparty/:$basemodulepath

# Manifest
manifest = manifests/site.pp

# current or future (3.8 only)
# parser = current

## Path to custom script
# config_version=

## Timeout for cache
environment_timeout = unlimited
 o<  

This setup works for environment "development" but not "master".


> *agent shell# puppet agent --onetime --test --environment master => Fail 
> with 404Error: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: Could not find class my_webserver for webserver-test1 on node 
> webserver-test1*


*agent shell# puppet agent --onetime --test --environment development => OK*


If I do "mv /etc/puppet/environments/master 
/etc/puppet/environments/mytest123" and restart the puppetserver mytest123 
environment works

*agent shell# puppet agent --onetime --test --environment mytest123 => OK*


If I do "mv /etc/puppet/environments/mytest123 
/etc/puppet/environments/master" and restart the puppetserver master 
environment FAILES again


> *agent shell# puppet agent --onetime --test --environment master => Fail 
> with 404Error: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: Could not find class my_webserver for webserver-test1 on node 
> webserver-test1*


So it is not the repo content but the name of the environment causing the 
problem I guess. 

Has someone seen this issue yet ??

Using "prefix: true" on r10k should fix the issue and generate unique 
environment names. 

Also renaming all git branches should solve the issue.

However I would like to know if this issue is known and if it still exists 
on Puppet 4.0 ?

Regards, 
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/cb8cb201-5524-4956-a