[Puppet Users] Re: Is there a way to publish a module via the Forge API?

[Amos Shapira]

No I haven't. This looks interesting especially if I could take advantage 
of it to deploy to private repos too (Gemfury.com or self-hosted Nexus, for 
instance)

On Saturday, 21 May 2016 01:41:24 UTC+10, Corey Osman wrote:
>
> Have you seen the dpl gem?
>
> https://github.com/travis-ci/dpl#puppet-forge
>
>
> Corey
>
> On Thursday, May 19, 2016 at 9:51:38 PM UTC-7, Amos Shapira wrote:
>>
>> Hello,
>>
>> I didn't find a way to upload a module to the Forge using the Forge API. 
>> Is this possible?
>>
>> I find it a bit weird that a tool which advocates "infrastructure as 
>> code" doesn't cater for options to script module uploads.
>>
>> Am I missing something?
>>
>> 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/fbfc3056-68f4-4902-81ea-a732a414d06b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a way to publish a module via the Forge API?

[Amos Shapira]

Thanks Rob.

We don't use Travis or Github and for now I'm the only one maintaining the 
module. We use Blackbox (https://github.com/StackExchange/blackbox) and 
hiera-eyaml-gpg (https://github.com/sihil/hiera-eyaml-gpg) to store shared 
secrets. If we get to doing this through our self-hosted Jenkins server 
then I'll probably look at providing the password to the job using the 
Credentials Plugin 
(https://cloudbees.zendesk.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs).

Cheers.

On Friday, 20 May 2016 21:08:14 UTC+10, Rob Nelson wrote:
>
> I love blacksmith, it's great. It does require the forge password be known 
> to the person running it, however.
>
> You can "level up" your deployments to allow others with write access to 
> your repo, but not the forge credentials, in a mature pipeline with Travis 
> CI's automated deployments . 
> Details on puppetforge deploys 
> , and an example of a 
> working .travis.yml 
>  
> (the secure string is generated by travis encrypt 
> ). This allows any 
> contributor to create a tag (usually with the voxpupuli-release gem 
>  and `rake 
> travis_release`, but also by creating a tag on GitHub). Travis kicks off a 
> build on the tag, and if the test specified in the deploy section goes 
> green, your module is published to the forge. That might be overkill for a 
> module maintained by one person, but it is pretty neat when you have a 
> distributed team and can't/don't want to share the forge password with 
> everyone.
>
> I'm sure you could get the same thing working with other services than 
> GitHub/Travis CI, those are just the pair I know.
>
> On Friday, May 20, 2016 at 3:48:16 AM UTC-4, garethr wrote:
>>
>> Hi Amos 
>>
>> On 20 May 2016 at 05:51, Amos Shapira  wrote: 
>> > Hello, 
>> > 
>> > I didn't find a way to upload a module to the Forge using the Forge 
>> API. Is 
>> > this possible? 
>> > 
>> > I find it a bit weird that a tool which advocates "infrastructure as 
>> code" 
>> > doesn't cater for options to script module uploads. 
>> > 
>>
>> It is indeed possible. Better that possible, there is even have a 
>> handy tool that provides a nice user interface for doing so. 
>>
>> https://github.com/voxpupuli/puppet-blacksmith 
>>
>> Blacksmith provides a number of useful commands for determining how 
>> you want to go about releasing your modules. The simplest is to just 
>> run: 
>>
>> rake module:release 
>>
>> The README has lots more details. 
>>
>> Gareth 
>>
>>
>> > Am I missing something? 
>> > 
>> > 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...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/puppet-users/8cbb7e19-dbf8-4f06-9a52-76ebb5c24287%40googlegroups.com.
>>  
>>
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>
>>
>> -- 
>> Gareth Rushgrove 
>> @garethr 
>>
>> devopsweekly.com 
>> morethanseven.net 
>> garethrushgrove.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/8e1f7ffe-3131-4392-8642-304156c895e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet server 4: hiera set up?

[dkoleary]

Unbelievable.  I'm a dumb-a##.  That was it.  Thank you very much.

# mv pm pm.yaml
# puppet lookup puppet::status
--- running
...


On Friday, May 20, 2016 at 2:42:40 PM UTC-5, R.I. Pienaar wrote:
>
>
>
> my guess is this should be pm.yaml 
>

-- 
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/ed4662c5-86c3-4184-af21-98c7253f6476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet server 4: hiera set up?

[R.I.Pienaar]

- Original Message -
> From: "Rob Nelson" 
> To: "puppet-users" 
> Sent: Friday, 20 May, 2016 21:36:25
> Subject: Re: [Puppet Users] puppet server 4: hiera set up?

> Doug,
> 
> You could add --trace to see where it's looking. I would also try tossing
> something into common, which requires NO facts, to ensure base hiera
> functionality before moving on to tiers dependent upon fact values.
> 
> 
> Rob Nelson
> rnels...@gmail.com
> 
> On Fri, May 20, 2016 at 3:11 PM, dkoleary 
> wrote:
> 
>> Hey;
>>
>> Before dumping a bunch of data into hiera data files, I wanted to run a
>> quick check to verify functionality.  This seems to be set up so I'm
>> suspecting my test isn't valid.  Could someone take a peek and confirm for
>> me?
>>
>> This is the set up:
>>
>> # h
>> pm
>>
>> # puppet config print hiera_config
>> /etc/puppetlabs/puppet/hiera.yaml
>>
>> # cat /etc/puppetlabs/puppet/hiera.yaml
>> ---
>> :backends:
>>   - yaml
>> :hierarchy:
>>   - "hosts/%{facts.hostname}"
>>   - "environments/%{facts.environment}"
>>   - "host_env/%{facts.env}"
>>   - "os/%{facts.osfamily}"
>>   - common
>> :yaml:
>>   :datadir: /etc/puppetlabs/code/hieradata
>>
>> # facter hostname
>> pm
>>
>> # cat /etc/puppetlabs/code/hieradata/hosts/pm

my guess is this should be pm.yaml

-- 
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/344859018.727155.1463773353025.JavaMail.zimbra%40devco.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet server 4: hiera set up?

[Rob Nelson]

Doug,

You could add --trace to see where it's looking. I would also try tossing
something into common, which requires NO facts, to ensure base hiera
functionality before moving on to tiers dependent upon fact values.


Rob Nelson
rnels...@gmail.com

On Fri, May 20, 2016 at 3:11 PM, dkoleary 
wrote:

> Hey;
>
> Before dumping a bunch of data into hiera data files, I wanted to run a
> quick check to verify functionality.  This seems to be set up so I'm
> suspecting my test isn't valid.  Could someone take a peek and confirm for
> me?
>
> This is the set up:
>
> # h
> pm
>
> # puppet config print hiera_config
> /etc/puppetlabs/puppet/hiera.yaml
>
> # cat /etc/puppetlabs/puppet/hiera.yaml
> ---
> :backends:
>   - yaml
> :hierarchy:
>   - "hosts/%{facts.hostname}"
>   - "environments/%{facts.environment}"
>   - "host_env/%{facts.env}"
>   - "os/%{facts.osfamily}"
>   - common
> :yaml:
>   :datadir: /etc/puppetlabs/code/hieradata
>
> # facter hostname
> pm
>
> # cat /etc/puppetlabs/code/hieradata/hosts/pm
> ---
> puppet::status: 'running'
>
> but the tests aren't showing anything:
>
> # hiera puppet::status
> nil
> # puppet lookup puppet::status
>
> The hiera call makes sense because it doesn't have access to host fact, as
> I understand it.  The puppet lookup command should have worked, though,
> right?
>
> Any hints/tips/suggestions greatly appreciated.
>
> Doug O'Leary
>
> --
> 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/d7754606-219a-49f3-9065-4f3bd52855b3%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/CAC76iT9ezn_sqn65Kkb%2BR6DueVEu5Sj8KtAfdMWCHZH-TXcq7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet server 4: hiera set up?

[dkoleary]

Hey;

Before dumping a bunch of data into hiera data files, I wanted to run a 
quick check to verify functionality.  This seems to be set up so I'm 
suspecting my test isn't valid.  Could someone take a peek and confirm for 
me?

This is the set up:

# h
pm

# puppet config print hiera_config
/etc/puppetlabs/puppet/hiera.yaml

# cat /etc/puppetlabs/puppet/hiera.yaml
---
:backends:
  - yaml
:hierarchy:
  - "hosts/%{facts.hostname}"
  - "environments/%{facts.environment}"
  - "host_env/%{facts.env}"
  - "os/%{facts.osfamily}"
  - common
:yaml:
  :datadir: /etc/puppetlabs/code/hieradata

# facter hostname
pm

# cat /etc/puppetlabs/code/hieradata/hosts/pm
---
puppet::status: 'running'

but the tests aren't showing anything:

# hiera puppet::status
nil
# puppet lookup puppet::status

The hiera call makes sense because it doesn't have access to host fact, as 
I understand it.  The puppet lookup command should have worked, though, 
right?

Any hints/tips/suggestions greatly appreciated.

Doug O'Leary

-- 
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/d7754606-219a-49f3-9065-4f3bd52855b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Can data type validation reference a variable for the possible enum values?

[David Karr]

Reading through "Learning Puppet 4", I noticed the ability to define 
parameter types with pretty specific constraints, like "Enum['foo','bar']", 
et cetera.

Is there any way for the list of possible enum values to be specified 
elsewhere and then referenced in the type specification?

-- 
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/0ab28fec-64ae-4593-96b5-40644968fb10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Logrotate module broken, string 'undef' now treated as undef

[Daniel Urist]

There doesn't seem to be an issue when I run my test code with "puppet
apply".

I've tried this under puppet agents v.4.5.0 and v.3.8.5

On Fri, May 20, 2016 at 10:56 AM, Matthaus Owens 
wrote:

> Daniel,
> Thanks for filing the ticket. I'll take a stab at reproducing it today.
> Did you only see it with puppet runs against a master, or also with local
> puppet apply?
>
> On Fri, May 20, 2016 at 8:20 AM, Daniel Urist  wrote:
>
>> I filed a bug: https://tickets.puppetlabs.com/browse/SERVER-1356
>>
>> On Fri, May 20, 2016 at 6:41 AM, JeremyCampbell <
>> jeremycampbel...@gmail.com> wrote:
>>
>>> I can confirm the same issue on Puppetserver v2.4.0
>>>
>>> --
>>> 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/62c4f502-e46b-4cef-9fc6-71767eb1d5c3%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/CAEo6%3DKaa43cJg%3Daddt%2B%3DTR1%2B%2BH0C8vm2eAmvYUevcqPuNkHNfg%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/CACD%3DwAfyDLQuTgOjF_UbLYB24g9KAnLYVmYybDGe6vL_iHrzdw%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/CAEo6%3DKa2S37btXmJd7idhr4d8Prs0YMz%2BGExO0x8ZZf2HpkF%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Logrotate module broken, string 'undef' now treated as undef

[Matthaus Owens]

Daniel,
Thanks for filing the ticket. I'll take a stab at reproducing it today. Did
you only see it with puppet runs against a master, or also with local
puppet apply?

On Fri, May 20, 2016 at 8:20 AM, Daniel Urist  wrote:

> I filed a bug: https://tickets.puppetlabs.com/browse/SERVER-1356
>
> On Fri, May 20, 2016 at 6:41 AM, JeremyCampbell <
> jeremycampbel...@gmail.com> wrote:
>
>> I can confirm the same issue on Puppetserver v2.4.0
>>
>> --
>> 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/62c4f502-e46b-4cef-9fc6-71767eb1d5c3%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/CAEo6%3DKaa43cJg%3Daddt%2B%3DTR1%2B%2BH0C8vm2eAmvYUevcqPuNkHNfg%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/CACD%3DwAfyDLQuTgOjF_UbLYB24g9KAnLYVmYybDGe6vL_iHrzdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Is there a way to publish a module via the Forge API?

[Corey Osman]

Have you seen the dpl gem?

https://github.com/travis-ci/dpl#puppet-forge


Corey

On Thursday, May 19, 2016 at 9:51:38 PM UTC-7, Amos Shapira wrote:
>
> Hello,
>
> I didn't find a way to upload a module to the Forge using the Forge API. 
> Is this possible?
>
> I find it a bit weird that a tool which advocates "infrastructure as code" 
> doesn't cater for options to script module uploads.
>
> Am I missing something?
>
> 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/f85e8e2c-906b-4f75-8cba-2ed1ffd1d6ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Logrotate module broken, string 'undef' now treated as undef

[Daniel Urist]

I filed a bug: https://tickets.puppetlabs.com/browse/SERVER-1356

On Fri, May 20, 2016 at 6:41 AM, JeremyCampbell 
wrote:

> I can confirm the same issue on Puppetserver v2.4.0
>
> --
> 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/62c4f502-e46b-4cef-9fc6-71767eb1d5c3%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/CAEo6%3DKaa43cJg%3Daddt%2B%3DTR1%2B%2BH0C8vm2eAmvYUevcqPuNkHNfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet/splunk Staging Dependency Cycle Issue

[Joseph Karns]

Good Morning:

I've started using puppetlabs/splunk module and I'm having a Dependency 
Cycle Issue. Can someone help

Error: Could not apply complete catalog: Found 1 dependency cycle:
(File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]
 
=> Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm] 
=> Package[splunkforwarder] => 
File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm])
Cycle graph written to /var/opt/lib/pe-puppet/state/graphs/cycles.dot.


digraph Resource_Cycles {
  label = "Resource Cycles"
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
 
-> "Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]" 
-> "Package[splunkforwarder]" -> 
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
 
-> "Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]" 
-> "Package[splunkforwarder]" -> "File[/opt/staging/splunk]" -> 
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
 
-> "Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]" 
-> "Package[splunkforwarder]" -> "File[/opt/staging/splunk]" -> 
"Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
 
-> "Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]" 
-> "Package[splunkforwarder]" -> "File[/opt/staging]" -> 
"File[/opt/staging/splunk]" -> 
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
"File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
 
-> "Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]" 
-> "Package[splunkforwarder]" -> "File[/opt/staging]" -> 
"File[/opt/staging/splunk]" -> 
"Staging::File[splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]"
}


heira

splunk::params::version: '6.3.3'
splunk::params::build: 'f44afce176d0'
splunk::params::scr_root: 'puppet:///software/splunk'<-- File bucket on 
Puppet Master
splunk::params::server: 'x.x.x.x'



Any information would be helpful.

Thanks
Joey

-- 
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/33e49d53-fe46-46b6-8452-ec13760c7052%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet 4 environments git feedback?

[dkoleary]

Thanks, all, for the information.  I appreciate it.  

Doug O'Leary

-- 
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/5abdf4e3-72be-47d3-b85e-5c37a789a135%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] the issues with thias/fooacl: filesystem ACL

[Sans]

On Friday, May 20, 2016 at 1:21:24 AM UTC+1, Ken Lareau wrote:
>
>  
> If the file changes, fooacl on its own won't notice the change and won't 
> reset the ACLs.  You need to notify the class to ensure it does catch 
> this.  We have something like this for ours that we put after the fooacl 
> resource:
>
> File[] ~> Class['::fooacl']
>
> Hopefully this helps.
>
>
I have something similar but is it actually directly related to the issue I 
described? I have this: 

concat { "${wp_root}/wp-config.php":
mode=> '0400',
require => Wpcli::Core::Download["download_wordpress_${title}"],
notify  => Class['::fooacl'],
}
 
fooacl::conf { "allow_${wordpress::wp_owner}_wp_config_${title}":
target  => "${wp_root}/wp-config.php",
permissions => [ "user:${wordpress::wp_owner}:r" ],
require => Concat[ "${wp_root}/wp-config.php" ],
}

I cannot figure out if there is fundamentally wrong with this or not. Any 
suggestions?

-San
 

-- 
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/32692633-ebef-4e16-9b12-d6519e7ed063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Logrotate module broken, string 'undef' now treated as undef

[JeremyCampbell]

I can confirm the same issue on Puppetserver v2.4.0

-- 
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/62c4f502-e46b-4cef-9fc6-71767eb1d5c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Logrotate module broken, string 'undef' now treated as undef

[JeremyCampbell]

I can confirm the same issue on puppetserver version: 2.4.0 with the latest 
version of the yo61/logrotate module

On Wednesday, May 18, 2016 at 11:33:26 PM UTC+2, Daniel Urist wrote:
>
> I have been using the yo61 logrotate module from puppetforge (
> https://forge.puppet.com/yo61/logrotate), which seems to be the most 
> popular, but it recently stopped working, with many errors about undefined 
> parameters.
>
> The issue seems to be the use of the string 'undef' as a default value; 
> for example:
>
> define logrotate::rule(
>> $create_owner   = 'undef',
>>
>  
> Later on in the code, there are comparisons against the actual string 
> 'undef'; for example:
>
>
>   if ($create_owner != 'undef') and ($create_mode == 'undef') {
>> fail("Logrotate::Rule[${name}]: create_owner requires create_mode")
>>}
>
>
> Regardless of whether this is best practice, these comparisons are now 
> failing, apparently because the string 'undef' is now treated as the value 
> undef. I've confirmed this by printing the string with notify (prints 
> nothing when it's 'undef'), and changing it to something else, which does 
> print.
>
> I'm not sure exactly when this changed or if it's intended behavior or a 
> bug, but it does seem odd that now apparently 'undef' === undef
>

-- 
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/ae2f4a1c-470c-4feb-b039-d4cbda644f30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Hiera 2.0 with Puppet 3.x

[Scott Briggs]

Does anyone have any experience with Hiera 2.0 with Puppet 3.x?  Is that 
even possible given the newer "all in one" architecture?

Cheers,
Scott

-- 
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/63e2178c-b784-41a9-ab03-da012f5d664f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Cannot alias definition, duplicate declaration

[Julie Iaccarino]

Hey all! I've got a bit of an oddity.

I've upgraded from 3.7 to 4.4 and gone over the upgrade checklist for my 
code, but I'm still getting some catalog errors.


> 2016-05-19 15:06:51 + Puppet (err): Could not retrieve catalog from 
> remote server: Error 400 on SERVER: Evaluation Error: Error while 
> evaluating a Resource Statement, Evaluation Error: Error while evaluating a 
> Resource Statement, Cannot alias Registry_value[register host key 
> Debug.1.00.2073 build copy c:\webservicestore.zip] to 
> ["HKEY_CURRENT_USER\\Software\\SimonTatham\\PuTTY\\SshHostKeys\\"]
>  
> at 
> /etc/puppetlabs/code/environments/production/modules/profiles/manifests/build/scp_copy.pp:5;
>  
> resource ["Registry_value", 
> "HKEY_CURRENT_USER\\Software\\SimonTatham\\PuTTY\\SshHostKeys\\##"]
>  
> already declared at 
> /etc/puppetlabs/code/environments/production/modules/profiles/manifests/build/scp_copy.pp:5
>  
> at 
> /etc/puppetlabs/code/environments/production/modules/profiles/manifests/build/scp_copy.pp:5:5
>  
> at 
> /etc/puppetlabs/code/environments/production/modules/profiles/manifests/build/util/zip_retrieve.pp:12
>  
> on node ##



It's nothing super fancy, just a SCP script on puppet:
define profiles::build::scp_copy ($sharename = $title, $source, 
$destination) {

# Add the host key to the server if it doesn't already exist.
# Without this, scp will fail in batch mode because the host might be 
spoofed.
registry_value { "register host key ${sharename}":
 ensure => present,
 path   => 
"HKEY_CURRENT_USER\\Software\\SimonTatham\\PuTTY\\SshHostKeys\\##", 

 type   => string,   
 data   => "###" 
}

# Copy the file specified in source to destination.
exec { "copy build ${sharename}":
 provider => 'powershell',
 command  => "pscp -batch -pw ## 
#@##:${source} 
${destination}"
}
}


Being utilized like:

profiles::build::scp_copy { "${buildType}.${buildNo} build copy 
${zipSaveAbsolutePath}":
source  => '${buildNo}\\${buildType}.${buildNo}.zip',
destination => '${zipSaveAbsolutePath}'
}

I'm sure it's something easy that I'm missing. But I'm quite stuck. Any 
ideas?

-- 
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/c695e60f-3bc6-4ab9-b197-b517139dc2e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a way to publish a module via the Forge API?

[Rob Nelson]

I love blacksmith, it's great. It does require the forge password be known 
to the person running it, however.

You can "level up" your deployments to allow others with write access to 
your repo, but not the forge credentials, in a mature pipeline with Travis 
CI's automated deployments . 
Details on puppetforge deploys 
, and an example of a 
working .travis.yml 
 
(the secure string is generated by travis encrypt 
). This allows any 
contributor to create a tag (usually with the voxpupuli-release gem 
 and `rake 
travis_release`, but also by creating a tag on GitHub). Travis kicks off a 
build on the tag, and if the test specified in the deploy section goes 
green, your module is published to the forge. That might be overkill for a 
module maintained by one person, but it is pretty neat when you have a 
distributed team and can't/don't want to share the forge password with 
everyone.

I'm sure you could get the same thing working with other services than 
GitHub/Travis CI, those are just the pair I know.

On Friday, May 20, 2016 at 3:48:16 AM UTC-4, garethr wrote:
>
> Hi Amos 
>
> On 20 May 2016 at 05:51, Amos Shapira > 
> wrote: 
> > Hello, 
> > 
> > I didn't find a way to upload a module to the Forge using the Forge API. 
> Is 
> > this possible? 
> > 
> > I find it a bit weird that a tool which advocates "infrastructure as 
> code" 
> > doesn't cater for options to script module uploads. 
> > 
>
> It is indeed possible. Better that possible, there is even have a 
> handy tool that provides a nice user interface for doing so. 
>
> https://github.com/voxpupuli/puppet-blacksmith 
>
> Blacksmith provides a number of useful commands for determining how 
> you want to go about releasing your modules. The simplest is to just 
> run: 
>
> rake module:release 
>
> The README has lots more details. 
>
> Gareth 
>
>
> > Am I missing something? 
> > 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/8cbb7e19-dbf8-4f06-9a52-76ebb5c24287%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> Gareth Rushgrove 
> @garethr 
>
> devopsweekly.com 
> morethanseven.net 
> garethrushgrove.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/1919e254-d7f5-4f50-a5b0-32b8c9df1259%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Migration to PuppetDB and Apache/Passenger setup

[Dirk Heinrichs]

Am 20.05.2016 um 11:36 schrieb christg76:

> Lastly, are there any packages for Puppet 4 available to use in a
> APache/passenger setup? I'm running Debian, and from Puppetlabs it
> looks everything is for PuppetServer.

Puppet 4 has no PuppetMaster running in Apache/Passenger anymore.
There's only PuppetServer, which is standalone.

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.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/7a470c71-071a-69ef-0f29-c46221fc0459%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Migration to PuppetDB and Apache/Passenger setup

[christg76]

Hi, I'm in the process of planning a Puppet Upgrade. The current setup uses 
the ActiveRecord functionality/gem to connect to a MySQL DB for stored 
configs, exported resources. I'm reading in the Puppet 4 Release Notes that 
support for ActiveRecord is removed. Is there any standard way to export 
and import the existing data from MySQL to PuppetDB? The current Puppet 
version is still 2.7, but will be upgraded to 3.8 before the switch to 
PuppetDB.
Lastly, are there any packages for Puppet 4 available to use in a 
APache/passenger setup? I'm running Debian, and from Puppetlabs it looks 
everything is for PuppetServer.

Any advice would be greatly appreciated.

Chris

-- 
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/a7f1fbbf-2273-4eaf-a70c-fcf901898575%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppetserver package for Ubuntu Xenial not yet available?

[Gareth Rushgrove]

On 18 May 2016 at 23:29, Martijn  wrote:
> That's excellent news Matthaus. Thanks.
>
> Op woensdag 18 mei 2016 20:04:18 UTC+2 schreef Matthaus Litteken:
>>
>> Martijn,
>> Yes, there is a plan for releasing Xenial packages. There are puppetserver
>> and puppetdb releases tentatively planned for tomorrow that will contain
>> Xenial support.
>>

Just to say I installed these successfully this morning.

You'll just need to add the Xenial puppet collection repository from:

wget https://apt.puppetlabs.com/puppetlabs-release-pc1-xenial.deb

Gareth


> --
> 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/c62a46c4-3447-4aab-ad19-0d9f57282108%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Gareth Rushgrove
@garethr

devopsweekly.com
morethanseven.net
garethrushgrove.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/CAFi_6yJy%3DE6VZrM4BgGxMMfudhmNhhhM6BLTauRD6zADK-zBpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a way to publish a module via the Forge API?

[Gareth Rushgrove]

Hi Amos

On 20 May 2016 at 05:51, Amos Shapira  wrote:
> Hello,
>
> I didn't find a way to upload a module to the Forge using the Forge API. Is
> this possible?
>
> I find it a bit weird that a tool which advocates "infrastructure as code"
> doesn't cater for options to script module uploads.
>

It is indeed possible. Better that possible, there is even have a
handy tool that provides a nice user interface for doing so.

https://github.com/voxpupuli/puppet-blacksmith

Blacksmith provides a number of useful commands for determining how
you want to go about releasing your modules. The simplest is to just
run:

rake module:release

The README has lots more details.

Gareth


> Am I missing something?
>
> 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/8cbb7e19-dbf8-4f06-9a52-76ebb5c24287%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Gareth Rushgrove
@garethr

devopsweekly.com
morethanseven.net
garethrushgrove.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/CAFi_6yLuq4iVt0w%3DzxZmLj6-Fdzr4uU6N8u1NGPqGSdo9KOBDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.