Re: [Puppet Users] Puppet Module Best Practice (Roles/Profiles)

There are times auto-loading resources from hiera data makes sense, such as mlocal users or sudoer.d snippets (though PLEASE use .each instead of create-resources!). These resources should absolutely be resources you in no way manage anywhere else. For sudoer.d, you might “include sudo;

Re: [Puppet Users] Puppet Module Best Practice (Roles/Profiles)

As a trivial example maybe we suddenly found that we needed to add a configuration file to a bunch of systems quickly. Because my coworker's class includes a generic call to 'create_resources("file")' we can arbitrarily add any file with any content by simply adding some data to Hiera.

Re: [Puppet Users] Puppet Module Best Practice (Roles/Profiles)

There appears to be contradiction here. If “one-off” changes for “new functionality” are needed, why are the changes going into a base/profile module ? Would some more specific and detailed examples be possible ? — "Sometimes I think the surest sign that

[Puppet Users] Puppet Module Best Practice (Roles/Profiles)

Hi all; I'm a Linux engineer who went through a typical growth period with Puppet and finally landed on the Roles and Profiles pattern which generally works well. I have a coworker that started on after me and doesn't like this pattern and having to update profiles or base modules when new

Re: [Puppet Users] puppet module repository w/ self signed ssl?

Am Dienstag, 5. Juni 2018 18:05:23 UTC+2 schrieb Josh Cooper: > > > > On Tue, Jun 5, 2018 at 8:52 AM, Sean > > wrote: > >> Hello, >> >> I'm wanting to use the module_repository setting in puppet.conf on my >> puppet5 master. The local repo mirror we've setup requires SSL, but has a >>

Re: [Puppet Users] puppet module repository w/ self signed ssl?

On Tue, Jun 5, 2018 at 8:52 AM, Sean wrote: > Hello, > > I'm wanting to use the module_repository setting in puppet.conf on my > puppet5 master. The local repo mirror we've setup requires SSL, but has a > self-signed cert. Is there a way to make puppet trust that cert? > > Mostly, I want to be

[Puppet Users] puppet module repository w/ self signed ssl?

Hello, I'm wanting to use the module_repository setting in puppet.conf on my puppet5 master. The local repo mirror we've setup requires SSL, but has a self-signed cert. Is there a way to make puppet trust that cert? Mostly, I want to be able to use puppet module search as a convenience

[Puppet Users] Puppet Module Gem Dependency

Cross-posting from Puppet Developers to get a wider audience. Hello All, I'm updating a module that will require a ruby gem (e.g. xml-simple) for one of the custom providers. How does Puppet make sure that the gem is available and installed when the module is installed? Does a *puppet module

Re: [Puppet Users] Puppet module and Hiera variable access

On Wednesday, July 20, 2016 at 4:42:59 AM UTC-5, Tobias Koeck wrote: > > Hi > > that worked. Thanks. > > So if I want to force the user to set the variables in Hiera I have to use > the hiera( .. ) function? > > That's an odd way to put it, but if I understand you correctly then yes. In other

Re: [Puppet Users] Puppet module and Hiera variable access

Hi that worked. Thanks. So if I want to force the user to set the variables in Hiera I have to use the hiera( .. ) function? Greetings Tobias On Mon, Jul 18, 2016 at 9:11 PM, Robert Story wrote: > On Mon, 18 Jul 2016 20:54:43 +0200 Tobias wrote: > TK> for testing Hiera a

Re: [Puppet Users] Puppet module and Hiera variable access

On Mon, 18 Jul 2016 20:54:43 +0200 Tobias wrote: TK> for testing Hiera a have written a common.yaml with TK> TK> qmonitoring::db::icinga2_ido_password: "mypwd34" TK> qmonitoring::db::icinga2_webdb_password: "mypwd544" TK> TK> and I have a module named qmonitoring with a class named TK> TK>

Re: [Puppet Users] Puppet module and Hiera variable access

You can use parameters as Rob suggests or specify the lookup yourself. $new_var = hiera('icinga2_ido_password') Also the var will be $::qmonitoring::db::new_var not the key you used. I recommend matching var to lookup key to make it easier to trace through the code. $icinga2_ido_password =

Re: [Puppet Users] Puppet module and Hiera variable access

You should investigate hiera automatic parameter lookup ( https://docs.puppet.com/hiera/latest/puppet.html#automatic-parameter-lookup). You need to make `icinga2_ido_password` a parameter of your class and then APL will "magically" populate that properly. Check out the article, which gets into

[Puppet Users] Puppet module and Hiera variable access

Hi, for testing Hiera a have written a common.yaml with qmonitoring::db::icinga2_ido_password: "mypwd34" qmonitoring::db::icinga2_webdb_password: "mypwd544" and I have a module named qmonitoring with a class named class qmonitoring::db { $new_var = $icinga2_ido_password, } where I try to

Re: [Puppet Users] Puppet Module directory structure

On 16/05/16 15:31, Harish Kothuri wrote: Hi, Can we customize the puppet module directory structure as i would like to separate the puppet modules and in-house written modules. Yes. The modulepath takes multiple entries - each should be the path to a directory containing modules. You should

Re: [Puppet Users] Puppet Module directory structure

Harish Kothuri writes: > Can we customize the puppet module directory structure as i would like to > separate the puppet modules and in-house written modules. Yes. You're looking at the 'modulepath' directive in environment.conf:

[Puppet Users] Puppet Module directory structure

Hi, Can we customize the puppet module directory structure as i would like to separate the puppet modules and in-house written modules. *Current Structure:* /etc/puppet/environment/production/modules/ contains all modules includes puppet forge Ex: ntp , stdlib, chocolatey and mypackg

Re: [Puppet Users] puppet module environment bug?

So when I replace list with upgrade and specify which module within that environment to upgrade, am I expecting that module's dependencies to be upgraded / installed in the common modules? I ask as we got quite the fright what that happened... I just tested with

Re: [Puppet Users] puppet module environment bug?

/etc/puppet/modules is available for all environments (if I am not mistaken). -- Lowe Schmidt | +46 723 867 157 On 29 January 2016 at 10:43, James Green wrote: > jamesg@puppet-master:/etc/puppet$ sudo puppet module list --environment > tools_office >

[Puppet Users] puppet module environment bug?

jamesg@puppet-master:/etc/puppet$ sudo puppet module list --environment tools_office /etc/puppet/environments/tools_office/modules └── garethr-docker (v4.1.1) /etc/puppet/modules ├── AlexCline-dirtree (v0.2.1) ├── AlexCline-fstab (v0.5.4) [ lots of others ] Why does puppet list the modules in the

Re: [Puppet Users] puppet module install cloudprovisioner Issue

You should probably use the gem provided with PE, not the system one. -- Lowe Schmidt | +46 723 867 157 On 24 December 2015 at 07:14, Sandeep Majety wrote: > > I am trying to intall Puppet Eneterprise in Ubuntu 14.04 machine... > > After running the puppet module

[Puppet Users] puppet module install cloudprovisioner Issue

I am trying to intall Puppet Eneterprise in Ubuntu 14.04 machine... After running the puppet module install puppetlabs-cloud_provisioner and testing puppet help, i am getting the below error ubuntu@ip-172-31-19-97:~$ puppet help Error: Could not autoload puppet/face/node/install: cannot load

Re: [Puppet Users] Puppet Module Writing - understanding clearly package dependency resolution

Thank you Gareth. What you state is what I was thinking. It looks like for me Solaris 10 isn't going to have an easy option for upgrading packages (and their dependencies) considering the environment in which I work. -- Warron French On Sun, Nov 29, 2015 at 7:49 AM,

Re: [Puppet Users] Puppet Module Writing - understanding clearly package dependency resolution

On 29 November 2015 at 03:54, Warron French wrote: > Hello, I am working on writing my first puppet module. I am pretty skilled > in writing complex shell (bash, ksh, sh) scripts so I have some questions in > general about writing a thorough puppet module. > > I want to

[Puppet Users] Puppet Module Writing - understanding clearly package dependency resolution

Hello, I am working on writing my first puppet module. I am pretty skilled in writing complex shell (bash, ksh, sh) scripts so I have some questions in general about writing a thorough puppet module. I want to write a single puppet module to support installation, configuration and service

Re: [Puppet Users] Puppet Module spec testing

Hi Ilja, Any reason you went with test-kitchen as opposed to beaker? i am trying to find a comparision between the two and where one fits better? as i am going to work with Ansible too i see that learning one tool that would work both in Ansible, and Puppet is a plus, however i am interested to

Re: [Puppet Users] puppet module - check if port is opened before running resource

In this case, you can have a fact that uses the code that you posted above. Facts are just Ruby so you can pretty much do whatever you need and return the boolean as the fact content. However, you may need to get a bit fancy and use a confine to ensure that only that one node is triggering the

Re: [Puppet Users] puppet module - check if port is opened before running resource

No, it is remote. I am deploying a application cluster that has some nodes dependencies, so basically in order to execute a script in one node I need to make sure first that the remote node is already listening on a specific port, if that node is not listening on that port I do not want to

[Puppet Users] puppet module - check if port is opened before running resource

Hello, I am writing a puppet module and I am looking into a way to have a validation before trying to execute something in puppet. For example: If host is listing on port 3306 { file { 'name': ensure => file, } } or If host is listing on port 3306 { include

Re: [Puppet Users] puppet module - check if port is opened before running resource

Is this the *local* host listening on that port, or some remote system? If it's the local host, then you would want to use a fact that calls something like netstat or ss and returns a Boolean based on the result of that port selection. You could also return all listening ports as a Hash and go

Re: [Puppet Users] Puppet Module spec testing

Hi, You're welcome to checkout our modules as well at https://github.com/unibet/. For instance https://github.com/unibet/puppet-vagrant. Some details about our testing mechanics: 1. rake used to manage the project. See https://github.com/unibet/puppet-vagrant/blob/master/Rakefile 2.

Re: [Puppet Users] Puppet Module spec testing

Hi Peter, On 04 Aug 2015, at 21:37, Peter Berghold salty.cowd...@gmail.com wrote: Is there a newer set of documents on doing Spec testing of Puppet modules than this link? https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing I am running into a brick wall getting this

Re: [Puppet Users] Puppet Module spec testing

On 4 August 2015 at 20:37, Peter Berghold salty.cowd...@gmail.com wrote: Is there a newer set of documents on doing Spec testing of Puppet modules than this link? https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing I am running into a brick wall getting this to work so I

Re: [Puppet Users] Puppet Module spec testing

I've got something similar I built a while ago (and need to update again since I'm back in the Puppet world). Magnum: https://github.com/tehmaspc/magnum It will help you create a new module dir with a bunch of puppet tools setup for you - including rspec-puppet for spec testing and serverspec

Re: [Puppet Users] Puppet Module spec testing

On 8/4/15 3:37 PM, Peter Berghold wrote: Is there a newer set of documents on doing Spec testing of Puppet modules than this link? https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing I am running into a brick wall getting this to work so I have to assume I'm doing

[Puppet Users] Puppet Module spec testing

Is there a newer set of documents on doing Spec testing of Puppet modules than this link? https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing I am running into a brick wall getting this to work so I have to assume I'm doing something wrong... -- You received this message

[Puppet Users] Puppet module testing

Is there a definitive guide somewhere that would guide me as to how to write Puppet module tests? In particular I'm interested in learning how to write a tasklist file. I keep seeing mention of such but nothing that helps... -- You received this message because you are subscribed to the Google

[Puppet Users] puppet module list upgrades-available

I have a need to report on the modules we have installed and for each: 1. The version installed 2. The latest version available to upgrade to Any ideas how to get this as I'm not seeing a puppet module command to match. [ Fairly convinced I cannot be the first to ask this too... ] Thanks,

Re: [Puppet Users] puppet module list upgrades-available

On 3/9/15 9:29 AM, James Green wrote: I have a need to report on the modules we have installed and for each: 1. The version installed 2. The latest version available to upgrade to Any ideas how to get this as I'm not seeing a puppet module command to match. [ Fairly convinced I cannot

Re: [Puppet Users] Puppet module

Yes, of course I have read it. I was trying to install the module with a puppet script instead of doing it in the commandline. The documentation said nothing about that. lørdag 14. februar 2015 19.52.45 UTC+1 skrev Hristo Mohamed følgende: Have you considered reading the documentation?

Re: [Puppet Users] Puppet module

- Original Message - | Trying to install the module vcsrepo with puppet, but really unsure how it | could be done. The commandline to install it is: | puppet module install puppetlabs-vcsrepo | Tried to install it this way, but that didn't work: | package { 'vcsrepo': | ensure =

Re: [Puppet Users] Puppet module

Have you considered reading the documentation? https://github.com/puppetlabs/puppetlabs-vcsrepo On Sat, Feb 14, 2015 at 5:37 PM, Bilal Ahmad bilaloslo...@gmail.com wrote: Trying to install the module vcsrepo with puppet, but really unsure how it could be done. The commandline to install it is:

[Puppet Users] Puppet module

Trying to install the module vcsrepo with puppet, but really unsure how it could be done. The commandline to install it is: puppet module install puppetlabs-vcsrepo Tried to install it this way, but that didn't work: package { 'vcsrepo': ensure = installed, } -- You

Re: [Puppet Users] puppet module for checking CVE's

Question is the goal of the factor output. From my point of view, only CVEs not implemented in the system are relevant (i.e. for reporting). CVEs already implemented are not really from interest to me. So if the standard behavior is, only show facts with CVEs not implemented yet and show all CVEs

Re: [Puppet Users] puppet module for checking CVE's

Would it be possible to side-load this into PuppetDB? For instance, instead of running the full list of checks with every run of puppet, have a cron job (or something) that runs the list and feeds the data directly into PuppetDB for the node. That would take the pressure off of each Puppet run

Re: [Puppet Users] puppet module for checking CVE's

On 10/12/14 5:16 PM, Felix Frank wrote: On 10/11/2014 02:22 AM, Garrett Honeycutt wrote: We could check if a file exists in a directory and if so, skip the fact. Suggest using /usr/local/etc/cve/fact_name What do you think? Sure, some thing in the file system. I suggest to not hard

Re: [Puppet Users] puppet module for checking CVE's

On 10/13/14 8:59 AM, Trevor Vaughan wrote: Would it be possible to side-load this into PuppetDB? For instance, instead of running the full list of checks with every run of puppet, have a cron job (or something) that runs the list and feeds the data directly into PuppetDB for the node.

Re: [Puppet Users] puppet module for checking CVE's

On 10/13/2014 06:36 PM, Garrett Honeycutt wrote: Hi Felix, I agree this should be configurable, though I'm not sure the best way to go about that. Facts do not take parameters, so I'm not sure what you mean by that. Best regards, -g Good point. You *could* manage an external fact

Re: [Puppet Users] puppet module for checking CVE's

Unfortunately, I very much share Felix's fear in getting swamped by facts. I mean, there are *thousands* of CVEs. Good goal though, I'll have to think about this. Trevor On Mon, Oct 13, 2014 at 12:41 PM, Garrett Honeycutt g...@garretthoneycutt.com wrote: On 10/13/14 8:59 AM, Trevor Vaughan

Re: [Puppet Users] puppet module for checking CVE's

On 10/13/2014 09:23 PM, Trevor Vaughan wrote: Unfortunately, I very much share Felix's fear in getting swamped by facts. I mean, there are *thousands* of CVEs. Yeah, but then... Would it be possible to side-load this into PuppetDB? ...this made me think of blackjack. And hookers ;-) But it

Re: [Puppet Users] puppet module for checking CVE's

On 10/11/2014 02:22 AM, Garrett Honeycutt wrote: We could check if a file exists in a directory and if so, skip the fact. Suggest using /usr/local/etc/cve/fact_name What do you think? Sure, some thing in the file system. I suggest to not hard code locations. This should be a parameter.

[Puppet Users] puppet module for checking CVE's

Hello, Published puppet-module-cve[1] to act as a framework for adding facts for specific CVE's that tell you if you are vulnerable to them. Inspiration came after ShellShock where I saw people had written modules with corresponding facts exclusively for that exploit. Our community needs a

Re: [Puppet Users] puppet module for checking CVE's

Hi Garrett, cool idea. I think it could use a dial to explicitly whitelist the facts that I want to be populated. Deploying an ever growing range of (sometimes expensive) checks to all agents, all of which will forever return false after patching, is not a merry perspective. What do you think?

Re: [Puppet Users] puppet module for checking CVE's

Granted I haven't completed taking a good look at the code yet, but to address Felix's concerns. What about a method of caching successful (ie: non-vulnerable) CVE fact results for an administratively configured time? This could limit the number of facts that have to run through their

Re: [Puppet Users] puppet module for checking CVE's

On 10/10/14 7:23 PM, Felix Frank wrote: Hi Garrett, cool idea. I think it could use a dial to explicitly whitelist the facts that I want to be populated. Deploying an ever growing range of (sometimes expensive) checks to all agents, all of which will forever return false after patching, is

Re: [Puppet Users] puppet module for checking CVE's

On 10/10/14 8:07 PM, Jeremy T. Bouse wrote: Granted I haven't completed taking a good look at the code yet, but to address Felix's concerns. What about a method of caching successful (ie: non-vulnerable) CVE fact results for an administratively configured time? This could limit the

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

Hi John/Felix, thanks for the suggestions, will try them out next week and come back with the results Stefan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to

[Puppet Users] Puppet module for Windows 2012 SNMP Service

Does anyone have a module or example puppet code for turning on SNMP server and setting the community on a Windows 2012 server? Matt -- 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

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

On 06/19/2014 02:12 PM, Stefan Heijmans wrote: class oracle_t { include install, sysctl } FWIW, I consider this bad form. You should qualify your class names, even if you include inside the same module. include oracle_t::install include oracle_t::sysctl It's not much more to type, and is

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

On 06/19/2014 02:12 PM, Stefan Heijmans wrote: Puppet module with all resources in 1 file === ... kernel.sem is available in /etc/sysctl.conf kernel.sem = 250 32000 100 128 kernel.shmall is available in /etc/sysctl.conf kernel.shmall = 1073741824

Re: [Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

Hi, the difference is in the /etc/sysctl.conf;' Puppet module with all resources in 1 file === After; /etc/sysctl.conf -rw-r--r--. 1 root root 2679 Jun 19 12:54 /etc/sysctl.conf fs.aio-max-nr = 1048576 fs.file-max = 6815744 kernel.core_uses_pid = 1

[Puppet Users] Puppet module 'issue' with sysctl provider (augeasproviders)

Hello, I've got 'something strange' with a Puppet module, using augeasproviders (v1.2.0 or master branch of today) on Puppet 3.6.2 Below a stripped version of it with the same results as the full version; It installs an Oracle preinstall rpm which also updates /etc/sysctl.conf settings and

[Puppet Users] Puppet module to install and configure libvirt on hosts and webvirtmgr on a separate server

Hi All, I got this fully working yesterday on CentOS 6.5 and uploaded it to github today: https://github.com/ITBlogger/puppet-kvm It's very crude, doesn't have any parameter validation or testing and requires hiera as written, but you may find it useful. At some point it would be interesting

[Puppet Users] puppet module permissions - librarian-puppet

I have noticed lately that on my development system (OS X) and my production Puppet master (CentOS 6.5) that when installing puppet modules using librarian-puppet the permissions of some modules and files is very restrictive to the point where the puppetmaster can't read the files. Some

Re: [Puppet Users] puppet module permissions - librarian-puppet

What umask are you using? R. On 21 Apr 2014 19:18, treydock treyd...@gmail.com wrote: I have noticed lately that on my development system (OS X) and my production Puppet master (CentOS 6.5) that when installing puppet modules using librarian-puppet the permissions of some modules and files is

Re: [Puppet Users] puppet module permissions - librarian-puppet

I'm using 0022 on no both desktop and puppet master. - Trey On Apr 21, 2014 2:02 PM, Robin Bowes robin.bo...@yo61.com wrote: What umask are you using? R. On 21 Apr 2014 19:18, treydock treyd...@gmail.com wrote: I have noticed lately that on my development system (OS X) and my production

[Puppet Users] puppet module install output is missing files for puppetlabs/firewall

On a CentOS 6.5 64-bit systems with Puppet 3.4.3 from the PuppetLabs repo: # puppet module install puppetlabs/firewall Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... Error: No such file

Re: [Puppet Users] puppet module install output is missing files for puppetlabs/firewall

Thanks for pointing this out! The problem is that one of the spec files (spec/acceptance/nodesets/default.yml) is a symlink to another .yml file in that directory (usually centos-64-x64.yml). The `puppet module install` command downloads the tarball to a cache directory in /var, extracts, then

Re: [Puppet Users] Puppet module template mentioned at contributor summit

We're currently arguing^w discussing the use of the params class in conjunction with hiera lookups and we've arrived at what I think is a pretty good pattern. Let me explain by way of example, using the venerable ntp application class ntp{ include ::ntp::params Class['::ntp::params']-

Re: [Puppet Users] Puppet module template mentioned at contributor summit

We could have been talking in my cube. My points when I'm discussing this with coworkers generally go like so... If you use this: class { name: } You will only be able to declare that name once. If you declare classes like this: include ::name include ::name::otherclass Then you will be

Re: [Puppet Users] Puppet module template mentioned at contributor summit

Hi Christopher, On 3 Mar 2014, at 17:55, Christopher Wood christopher_w...@pobox.com wrote: We could have been talking in my cube. My points when I'm discussing this with coworkers generally go like so... If you use this: class { name: } You will only be able to declare that name

Re: [Puppet Users] Puppet module template mentioned at contributor summit

(inline) On Mon, Mar 03, 2014 at 06:24:47PM +, Robin Bowes wrote: Hi Christopher, On 3 Mar 2014, at 17:55, Christopher Wood [1]christopher_w...@pobox.com wrote: We could have been talking in my cube. My points when I'm discussing this with coworkers generally go like

Re: [Puppet Users] Puppet module template mentioned at contributor summit

(also inline) On 3 Mar 2014, at 19:25, Christopher Wood christopher_w...@pobox.com wrote: (inline) On Mon, Mar 03, 2014 at 06:24:47PM +, Robin Bowes wrote: Additionally, it creates two places in which the parameters can be automatically set. eg. ntp::install::package_name and

Re: [Puppet Users] Puppet module template mentioned at contributor summit

On 28 February 2014 10:20, Craig Dunn cr...@craigdunn.org wrote: The main difference between Gareth's current params.pp and the 'defaults.pp' model I was suggesting is that in the Gareth's pattern the params class is inherited by the base class, and all the component subclasses reference the

Re: [Puppet Users] Puppet module template mentioned at contributor summit

On 1 March 2014 09:38, Gareth Rushgrove gar...@morethanseven.net wrote: On 28 February 2014 10:20, Craig Dunn cr...@craigdunn.org wrote: The main difference between Gareth's current params.pp and the 'defaults.pp' model I was suggesting is that in the Gareth's pattern the params class is

Re: [Puppet Users] Puppet module template mentioned at contributor summit

The main difference between Gareth's current params.pp and the 'defaults.pp' model I was suggesting is that in the Gareth's pattern the params class is inherited by the base class, and all the component subclasses reference the variables explicitly in the scope of base::params eg: service {

Re: [Puppet Users] Puppet module template mentioned at contributor summit

Ok, I think we are talking about the same thing, then: https://github.com/stdmod/puppet-skeleton-standard/blob/develop/manifests/init.pp.erb should follow what you described as defaults.pp patterns , just it uses a class named params and not default. On Friday, February 28, 2014 11:20:57 AM

Re: [Puppet Users] Puppet module template mentioned at contributor summit

This is cool, though I realise that it's a (self confessed) opinionated module design, the only thing that really stands out for me is that it follows a rather old, and limited, 'params.pp' pattern. There is no place for Hiera in this model without hard coding hiera lookup functions in the

Re: [Puppet Users] Puppet module template mentioned at contributor summit

Craig, Not sure to have understood the difference between a defaults.pp pattern and a params.pp pattern, given that I suppose that if there were parameters in the main module class of Gareth's example they would inherit values in params.pp exactly as the defaults example you've written. Can be

[Puppet Users] puppet module generate skeleton not working on PE?

Hi I'm wondering if anybody has successfully managed to get any `puppet module generate` templates (e.g. https://github.com/garethr/puppet-module-skeleton) working on a Puppet Enterprise box? I've tried both of the github skeleton modules on two different versions of PE, but not joy. Seems

Re: [Puppet Users] Puppet module template mentioned at contributor summit

On Wed, Feb 05, 2014 at 06:38:24PM +0100, Gareth Rushgrove wrote: This came up in discussion a couple of times at the Puppet contributor summit at Config Management Camp in Gent over the last couple of days so I thought I'd write up. A while ago I put together a pretty complete/opinionated

[Puppet Users] puppet module generate skeleton not working on PE?

Hi, I am not sure on the underlying reasons but this doesnt work under the root account. I ran into the same issue when I was playing with it on a dev box. Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group

[Puppet Users] Puppet module template mentioned at contributor summit

This came up in discussion a couple of times at the Puppet contributor summit at Config Management Camp in Gent over the last couple of days so I thought I'd write up. A while ago I put together a pretty complete/opinionated skeleton for puppet modules. Especially if you're not too familiar with

Re: [Puppet Users] Puppet module template mentioned at contributor summit

Thank you Gareth. Your module skeleton has helped my module development tremendously. Even though I created my own, differently opinionated, fork most of the skeleton is the same and your effort is greatly appreciated. On Wed, Feb 5, 2014 at 9:38 AM, Gareth Rushgrove gar...@morethanseven.net

[Puppet Users] Puppet module testing code coverage...

Afternoon all I've read a fair few blogs, slideshares and other sources recently around Module testing in Puppet, and it has spurned me on to start writing a test framework around our internal modules... Yes, we aren't currently testing our internal modules... Yes, we *should *be, and yes, I

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

On Fri, Sep 20, 2013 at 7:36 AM, Rainer Weinhold redsa...@gmail.com wrote: i just downloaded 3.3 for windows (w7,x64) and got the same error. output : C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet module install simondaen/iis --debug --trace Notice: Preparing to install into

Re: [Puppet Users] puppet module

On 10/8/13 2:27 PM, John wrote: I need to write a puppet SSHD module that does the following: First I have 5 different operating systems to install to: Red Hat, Free BSD, AIX, Ubuntu, and SuSE. The second requirements: If the host file contains an entry of host-A.domain.com (for

[Puppet Users] puppet module

I need to write a puppet SSHD module that does the following: First I have 5 different operating systems to install to: Red Hat, Free BSD, AIX, Ubuntu, and SuSE. The second requirements: If the host file contains an entry of host-A.domain.com (for example) then I need ssh-config1 installed.

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

i just downloaded 3.3 for windows (w7,x64) and got the same error. output : C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet module install simondaen/iis --debug --trace Notice: Preparing to install into M:/.puppet/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Error:

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

Are your results of `puppet module install simondaen/iis --debug --trace` similar to what the others were getting? On Wed, Sep 18, 2013 at 1:52 PM, Samuel Huang samhuan...@gmail.com wrote: Yeah I rebooted, and it still didn't work. On Monday, September 16, 2013 1:40:34 PM UTC-7, Rob

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

yes On Thu, Sep 19, 2013 at 1:08 PM, Rob Reynolds r...@puppetlabs.com wrote: Are your results of `puppet module install simondaen/iis --debug --trace` similar to what the others were getting? On Wed, Sep 18, 2013 at 1:52 PM, Samuel Huang samhuan...@gmail.comwrote: Yeah I rebooted, and it

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

Yeah I rebooted, and it still didn't work. On Monday, September 16, 2013 1:40:34 PM UTC-7, Rob Reynolds wrote: Yes, that is the one that I meant. I know you hate hearing this question, but did you reboot after you removed it (prior to module install) for full effect? On Mon, Sep 16, 2013

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

Can you determine if the cert is also under Machine certificate store and not just the Current User certificate store? On Fri, Sep 13, 2013 at 1:27 AM, Samuel Huang samhuan...@gmail.com wrote: I deleted the cert you mentioned *(thatwte-timestamping.png)*, but I still have the same error

[Puppet Users] puppet module generate using wrong name for directory?

Hi, I'm looking into writing proper modules and starting off with puppet module generate but it seems the tool uses an invalid name for the directory. When i specify mymodule as a name it tells me I need to use a dash separated name and when I use myname-mymodule then the module gets generated

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

For what it's worth, I had the same problem and figured out the particular cert on Windows 7 (64bit) that was causing the issue: -- [Subject] CN=Thawte Timestamping CA, OU=Thawte Certification, O=Thawte,

[Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

Hello, I have a fresh install of puppet 3.2.3. on windows 8. I try to install the iis module (https://forge.puppetlabs.com/simondean/iis) with the command: puppet module install simondean/iis and it gives me *C:\Program Files (x86)\Puppet Labs\Puppetpuppet module install simondean/iis*

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

On Tue, Jul 16, 2013 at 2:50 AM, Arno den Uijl arnodenu...@gmail.comwrote: Hello, I have a fresh install of puppet 3.2.3. on windows 8. I try to install the iis module (https://forge.puppetlabs.com/simondean/iis) with the command: puppet module install simondean/iis and it gives me

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

I thought i tried the debug and trace options but i this trace was new for me. I looked through the code and I think that it was caused by the fact that there were some certificates installed with the same name. I deleted some from my certificate store and now it runs correct. Thanks for the

Re: [Puppet Users] puppet module install simondean/iis gives error Error: cert already in hash table

On Tue, Jul 16, 2013 at 11:19 AM, Arno den Uijl arnodenu...@gmail.comwrote: I thought i tried the debug and trace options but i this trace was new for me. I looked through the code and I think that it was caused by the fact that there were some certificates installed with the same name. I

[Puppet Users] puppet module search using an HTTP proxy

Can anyone confirm that PE 3.0 supports this? I exported $http_proxy correctly, I beleive. $ puppet module search something Notice: Searching *https://forge.puppetlabs.com*https://forge.puppetlabs.com/... Error: Could not connect to *https://forge.puppetlabs.com*https://forge.puppetlabs.com/

  1   2   >