Re: [Puppet Users] Code coverage for puppet resources

Looks like there are few issues open like these: https://github.com/rodjek/rspec-puppet/issues/285 https://github.com/rodjek/rspec-puppet/issues/158 If anyone knows a way in Rakefile to exclude from coverage I'd be greatful. -- You received this message because you are subscribed to the

[Puppet Users] FreeBSD 8.x: Warning: Found multiple default providers for package: pkgng, freebsd; using pkgng

Hey there, Puppet 3.8.1 under FreeBSD 8.x (yes, I know it's EOL). I'm seeing the following warning when my manifest runs: Warning: Found multiple default providers for package: pkgng, freebsd; using pkgng I've set a provider in site.pp (and verified that that portion of the manifest has

[Puppet Users] puppet-agent package on FreeBSD

All, I keep seeing updates about a new release of a standalone puppet agent. Other than small file size and a possible reduced dependency set, is there any useful point in porting it to FreeBSD? Right now, on FreeBSD, pkg shows the following subset of things for a "pkg search puppet" (there

Re: [Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

I actually take the opposite approach. Modules from the forge go in a directory named "forge_modules" and r10k will leave anything located in modules alone. From r10k.yaml: forge 'http://forge.puppetlabs.com' moduledir 'forge_modules' On Friday, June 17, 2016 at 5:28:42 PM UTC-4, Rob

Re: [Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

r10k will deploy the modules listed in the Puppetfile into the modules directory. If you need some local (to the controlrepo) modules that are not deployed from the Puppetfile, the recommendation is to add them to a directory called site, dist, or similar, and create a file called environment.conf

[Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

r10k deployment is failing, if my repo paths has "modules" in it . if I change modules to any other word or even module it works fine . In order to correctly map environment on my puppet master I need r10k to map repo as /etc/puppetlabs/code/environments/production [branch name ] /

Re: [Puppet Users] Puppet only partially applying configuration

On Tue, Jun 7, 2016 at 12:15 PM, Andrew wrote: > I have encountered a problem when running puppet on Windows. My > environment is as follows: > > Puppet master: > CentOS 6.5 > puppetserver 2.3.1 > > Client: > Windows 2012 R2 > Puppet 3.8.7 > > What happens: > > I provision a

Re: [Puppet Users] clean msi installs on windows -- removing .msi file after

You could set up a file resource with ensure => absent and set up a relationship[1] to ensure it is checked after the MSI install. Another thing you would also look at with respect to Windows software management is Chocolatey[2][3]. [1]

RE: [Puppet Users] Basic syntax and learning problems

> From: puppet-users@googlegroups.com [mailto:puppet- > us...@googlegroups.com] On Behalf Of Peter Bukowinski > > Fortunately, facter has separate facts for most items in the os fact hash. > Keep in mind you can see all the facts available to your client by running > ‘sudo facter -p’ Thanks.

[Puppet Users] Re: [Puppet-dev] Re: Modules Triage Time Change

>> For those of you in APAC, we apologize for the still-inconvenient time >> slot. Feel free to reply here with ideas! >> >> > I just talked to Hunter on IRC. Maybe we can flip flop the times of the > meeting. For example 9:00UTC and the next week 17:00UTC. This would allow > us a kind of US

Re: [Puppet Users] Basic syntax and learning problems

>> On Jun 17, 2016, at 9:50 AM, Edward Ned Harvey (puppet) >> wrote: >> >> From: puppet-users@googlegroups.com [mailto:puppet- >> us...@googlegroups.com] On Behalf Of Peter Bukowinski >> >> Hi Edward, >> >> With puppet 3.7, all facts are "stringified" by default,

[Puppet Users] How to have a Puppet module install a particular version of something (docker, for instance)

I'm stepping through "Puppet for Containerization ". The very first exercise fails to start up the docker service, apparently because of an invalid command-line

[Puppet Users] Re: Modules Triage Time Change

Am Donnerstag, 26. Mai 2016 18:31:35 UTC+2 schrieb Hunter Haugen: > > Hello, > > tl;dr Puppet Modules Community Triage meeting is moving to 17:00-18:00 UTC > > This is a quick note that in the last Puppet Modules Community Triage > meeting we discussed a change in the specified time that the

RE: [Puppet Users] Basic syntax and learning problems

> From: puppet-users@googlegroups.com [mailto:puppet- > us...@googlegroups.com] On Behalf Of Peter Bukowinski > > Hi Edward, > > With puppet 3.7, all facts are "stringified" by default, meaning hashes are > flattened to strings. If you've got facter 2.0 or greater, you can change this > behavior

Re: [Puppet Users] Code coverage for puppet resources

Well for example if i use your puppet-module-skeleton... create a module that uses the rspec-puppet-facts for centos 5,6,7. include ::selinux (jfryman/selinux) in coverage report it shows the following missing: Package[policycoreutils-devel] Package[policycoreutils-python]

Re: [Puppet Users] Basic syntax and learning problems

Hi Edward, With puppet 3.7, all facts are "stringified" by default, meaning hashes are flattened to strings. If you've got facter 2.0 or greater, you can change this behavior do you can access hash keys individually.

[Puppet Users] Basic syntax and learning problems

Running puppet 3.7.4 I am new to puppet, and learning the syntax. For learning, I open up two terminals, where I "vi foo.pp" in one terminal, and I "puppet apply foo.pp" on the other terminal. Using this: node default { notify{"syntax1": message => $facts['osfamily'] } } I

Re: [Puppet Users] Code coverage for puppet resources

On 17 June 2016 at 15:24, Chris Denneen wrote: > Gareth, > > I know this thread is old but do you have a way in the Rakefile to exclude > the dependent modules? > For example dependent modules that include different package resources based > on OSfamily and version are

Re: [Puppet Users] Code coverage for puppet resources

Gareth, I know this thread is old but do you have a way in the Rakefile to exclude the dependent modules? For example dependent modules that include different package resources based on OSfamily and version are something that module controls and tests I just need to make sure that the module

[Puppet Users] Re: check if the package is installed and compare the version

Ithank you I understand, I do not use puppet as he would really Le vendredi 17 juin 2016 11:23:45 UTC+2, puppetstan a écrit : > > Hi, > > > I'm not an expert on puppet and I have some syntax problems > > > I would check if the package is installed and compare the version of the > package with

Re: [Puppet Users] Issue copying files if package exists

Rob Nelson wrote: > Modeling state can be tricky. It's pretty easy for a human to > understand conditionals like "If a package is installed, install a > file," but for state modeling, resources are best defined as either > managed or unmanaged, not somewhere in between. It's important to > keep

Re: [Puppet Users] check if the package is installed and compare the version

HI Stanislas On 17 June 2016 at 10:23, puppetstan wrote: > Hi, > > > I'm not an expert on puppet and I have some syntax problems > > > I would check if the package is installed and compare the version of the > package with the version I would like to see installed > >

[Puppet Users] check if the package is installed and compare the version

Hi, I'm not an expert on puppet and I have some syntax problems I would check if the package is installed and compare the version of the package with the version I would like to see installed IF the package is installed with the correct version DO NOTHING BUT if it is not installed or

Re: [Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo

Matt, take the src rpm that suits your needs. `mkdir -p rpm/{RPMS/x86_64,RPMS/noarch,SRPMS,SPECS,SOURCES,BUILD,BUILDROOT}` rpmbuild --rebuild puppet[whatever].srpm hit ctrl-c before it finishes. This will leave the .spec file and the source tarball in the SPECS and SOURCES dirs respectively.