On Friday, February 9, 2018 at 4:00:48 PM UTC-6, Albert Shih wrote:
>
> Hi,
>
> I would like to know how you or what's best practice to manage tag in
> exported resources.
>
> For example I have two hosts H1 and H2->100, and I want export file_line
> from H2->100
> to H1.
>
> So or I use a
Hello Team,
i am getting below error when trying to do puppet run. i am not sure how to
solve this, can pointers would be helpful.
Info: starting applying configuration to int-ams-ns01 at
http://int-ams-ns01:80/nitro/v1/
Info: Using configured environment 'staging'
Info: Retrieving pluginfact
Hi,
Currently our infrastructure and code is written with and run by puppet 4
opensource.
We are using https://yum.puppetlabs.com/el/7/PC1/x86_64/ repos for updates
of our installed software, puppetserver, puppetdb, puppet agent.
Since puppet 5 was released the puppet 5 packages shifted to ano
On Mon, 12 Feb 2018, at 17:43, Sven vd wrote:
> Hi,
>
> Currently our infrastructure and code is written with and run by puppet 4
> opensource.
>
> We are using https://yum.puppetlabs.com/el/7/PC1/x86_64/ repos for updates
> of our installed software, puppetserver, puppetdb, puppet agent.
>
Close, the PE2016.4 LTS uses Puppet 4 and is supported through October
2018.
--eric0
On Monday, February 12, 2018 at 9:15:20 AM UTC-8, R.I. Pienaar wrote:
>
>
>
> On Mon, 12 Feb 2018, at 17:43, Sven vd wrote:
> > Hi,
> >
> > Currently our infrastructure and code is written with and run by pu
Thanks, very clear answers
For reference, you can map puppet versions with PE releases by checking the
overview page
https://puppet.com/docs/pe/2017.3/overview/component_versions_in_recent_pe_releases.html
On Monday, February 12, 2018 at 6:20:25 PM UTC+1, Eric Sorenson wrote:
>
> Close, the PE
On Tue, Feb 6, 2018 at 3:04 AM, SCHAER Frederic
wrote:
> Hi,
>
>
>
> On my dev puppetserver, I have :
>
> # puppet config print environmentpath
>
> /puppet/code/envs
>
>
>
> # grep env /etc/puppetlabs/puppet/puppet.conf
>
> environmentpath = /puppet/code/envs
>
> environment = preprod
>
