[Puppet Users] in-module data with hiera
hello,
Till now hiera-puppet was the only way I know that allowed hiera data to
be loaded from inside a module.
The problem with this was that it was still subject to the site specific
hierarchy which means a module author had a pretty hard time to store
his data in a proper way in his module thus perpetuating the use of the
params classes pattern.
Now that Puppet 3 is out and it's gem extensible I can finally try some
ideas I had but put off implementing because it was too hard to install
and distribute these extensions.
I propose extending the module layout with a data/ directory that can go
into each module and in this data directory would live a hiera config
file (optionally) and module specific data:
your_module
├── data
│ ├── hiera.json
│ └── osfamily
│ ├── Debian.json
│ └── RedHat.json
└── manifests
└── init.pp
Here the data/hiera.json is optional and specifies a hierarchy that the
module author chooses and is unique to the specific backend.
The default contents would be this is the file is absent:
{hierarchy: [osfamily/%{osfamily}, common]}
But a module author can pick anything there, should even be able to rely
on facts that is shipped with the module in its lib dir since that'll
get pluginsynced out before compile time:
Now given the data files for Redhat:
{apache::package : httpd}
...and Debian:
{apache::package : apache2}
And your main hiera site config being something like:
:backends: - json
- module_json
You should be able to just write module code like this:
class apache($package=apache) {
package{$package: ensure = present}
}
If no data is specified in the site hiera backends then this will use
the in-module hierarchy and data and just do the right thing on RedHat
and Debian systems but as always the site can still override the data
using hard coding, site specific data, ENCs etc.
So the important thing here is the module author has control over the
hierarchy that gets used when the data in his module gets loaded. The
site can has its own hierarchy policy but this backend will only use
the hierarchy that is recorded in the module by its author.
If you want to play with this idea on your Puppet 3 install just do 'gem
install hiera-module-json'
So I am looking for feedback from the community on this pattern, will it
solve the problem of author-supplied module data better than we have
today? I've heard this problem brought up quite a lot so keen to hear
feedback.
I'd imagine eventually a backend like this might be a hard-coded backend
shipped with puppet and always there as the lowest priority backend
below any that the site might specify in their site wide hiera config so
everyone can rely on this being there and with the new lookup helpers
this should also be backward compatible - old Puppets or ones who
specifically disable the hiera indirector will just not have data and
will need to supply it some other way.
---
R.I.Pienaar
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] multiple puppet masters on multiple subnets
Thanks guys, I really appreciate the responses here. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/xGWoov-8j58J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] in-module data with hiera
This is -exactly- what I've wanted in my modules since I heard of
Hiera and I am strongly supporting this proposal. I'll be
experimenting with your gem. I can't give this enough support as this
is what I wanted since Hiera began. It'll make supporting multiple
distros/operating systems much easier for modules on the forge.
On Sun, Sep 30, 2012 at 5:37 AM, R.I.Pienaar r...@devco.net wrote:
hello,
Till now hiera-puppet was the only way I know that allowed hiera data to
be loaded from inside a module.
The problem with this was that it was still subject to the site specific
hierarchy which means a module author had a pretty hard time to store
his data in a proper way in his module thus perpetuating the use of the
params classes pattern.
Now that Puppet 3 is out and it's gem extensible I can finally try some
ideas I had but put off implementing because it was too hard to install
and distribute these extensions.
I propose extending the module layout with a data/ directory that can go
into each module and in this data directory would live a hiera config
file (optionally) and module specific data:
your_module
├── data
│ ├── hiera.json
│ └── osfamily
│ ├── Debian.json
│ └── RedHat.json
└── manifests
└── init.pp
Here the data/hiera.json is optional and specifies a hierarchy that the
module author chooses and is unique to the specific backend.
The default contents would be this is the file is absent:
{hierarchy: [osfamily/%{osfamily}, common]}
But a module author can pick anything there, should even be able to rely
on facts that is shipped with the module in its lib dir since that'll
get pluginsynced out before compile time:
Now given the data files for Redhat:
{apache::package : httpd}
...and Debian:
{apache::package : apache2}
And your main hiera site config being something like:
:backends: - json
- module_json
You should be able to just write module code like this:
class apache($package=apache) {
package{$package: ensure = present}
}
If no data is specified in the site hiera backends then this will use
the in-module hierarchy and data and just do the right thing on RedHat
and Debian systems but as always the site can still override the data
using hard coding, site specific data, ENCs etc.
So the important thing here is the module author has control over the
hierarchy that gets used when the data in his module gets loaded. The
site can has its own hierarchy policy but this backend will only use
the hierarchy that is recorded in the module by its author.
If you want to play with this idea on your Puppet 3 install just do 'gem
install hiera-module-json'
So I am looking for feedback from the community on this pattern, will it
solve the problem of author-supplied module data better than we have
today? I've heard this problem brought up quite a lot so keen to hear
feedback.
I'd imagine eventually a backend like this might be a hard-coded backend
shipped with puppet and always there as the lowest priority backend
below any that the site might specify in their site wide hiera config so
everyone can rely on this being there and with the new lookup helpers
this should also be backward compatible - old Puppets or ones who
specifically disable the hiera indirector will just not have data and
will need to supply it some other way.
---
R.I.Pienaar
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] err: Signing certificate error
Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using pson* *debug: Failed to load library 'selinux' for feature 'selinux'* *debug: Failed to load library 'ldap' for feature 'ldap'* *debug: /File[/home/ubuntu/.puppet/ssl/private_keys]: Autorequiring File[/home/ubuntu/.puppet/ssl]* *debug: /File[/home/ubuntu/.puppet/ssl/certs]: Autorequiring File[/home/ubuntu/.puppet/ssl]* *debug: /File[/home/ubuntu/.puppet/ssl/private]: Autorequiring File[/home/ubuntu/.puppet/ssl]* *debug: /File[/home/ubuntu/.puppet/var]: Autorequiring File[/home/ubuntu/.puppet]* *debug: /File[/home/ubuntu/.puppet/var/state]: Autorequiring File[/home/ubuntu/.puppet/var]* *debug: /File[/home/ubuntu/.puppet/ssl/certificate_requests]: Autorequiring File[/home/ubuntu/.puppet/ssl]* *debug: /File[/home/ubuntu/.puppet/var/lib]: Autorequiring File[/home/ubuntu/.puppet/var]* *debug: /File[/home/ubuntu/.puppet/var/run]: Autorequiring File[/home/ubuntu/.puppet/var]* *debug: /File[/home/ubuntu/.puppet/ssl/certs/ca.pem]: Autorequiring File[/home/ubuntu/.puppet/ssl/certs]* *debug: /File[/home/ubuntu/.puppet/ssl/public_keys]: Autorequiring File[/home/ubuntu/.puppet/ssl]* *debug: /File[/home/ubuntu/.puppet/var/facts]: Autorequiring File[/home/ubuntu/.puppet/var]* *debug: /File[/home/ubuntu/.puppet/ssl]: Autorequiring File[/home/ubuntu/.puppet]* *debug: Finishing transaction 69996349432740* *debug: Using cached certificate for test* *debug: Using cached certificate for test* *debug: Using cached certificate_request for test* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using pson* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using pson* *warning: Signing certificate ... Failed* *err: Signing certificate error: Error 403 on SERVER: Forbidden request: domU-12-31-39-06-8A-D7.compute-1.internal(10.208.141.33) access to /certificate_status/test [save] at line 123* * * I guess problem was on my auth.conf so i append: *# Allow unauthenticated access to certificates:* * * *path /certificate_status* *method save* *auth any* *allow test* * * *path /certificate/ca* *auth no* *method find* *allow ** * * *path /certificate/* *auth no* *method find* *allow ** But i get the same error. Thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/e-x7Jo5YDxEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] err: Signing certificate error
On Sun, Sep 30, 2012 at 1:02 PM, Ignasi López ignasi.lo...@mmip.es wrote: Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I can't prove it but I think you're forgetting to sudo puppet run the command again with sudo? or do it as root -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] err: Signing certificate error
I can't run the command with sudo: sudo puppet help node_aws err: no such file to load -- puppet/face/node/install err: Try 'puppet help help help' for usage It's permission problem??? Thanks! On Sunday, September 30, 2012 10:06:26 PM UTC+2, Clarence Beeks wrote: On Sun, Sep 30, 2012 at 1:02 PM, Ignasi López ignasi...@mmip.esjavascript: wrote: Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I can't prove it but I think you're forgetting to sudo puppet run the command again with sudo? or do it as root -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/DgRbhJj4PusJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] err: Signing certificate error
in fact i can't use puppet as a root: *sudo puppet help* *err: no such file to load -- puppet/face/node/install* *err: Try 'puppet help help help' for usage* On Sunday, September 30, 2012 11:16:56 PM UTC+2, Ignasi López wrote: I can't run the command with sudo: sudo puppet help node_aws err: no such file to load -- puppet/face/node/install err: Try 'puppet help help help' for usage It's permission problem??? Thanks! On Sunday, September 30, 2012 10:06:26 PM UTC+2, Clarence Beeks wrote: On Sun, Sep 30, 2012 at 1:02 PM, Ignasi López ignasi...@mmip.es wrote: Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test * I can't prove it but I think you're forgetting to sudo puppet run the command again with sudo? or do it as root -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/rqmJXluUQxgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] err: Signing certificate error
On Sun, Sep 30, 2012 at 2:22 PM, Ignasi López ignasi.lo...@mmip.es wrote: in fact i can't use puppet as a root: *sudo puppet help* *err: no such file to load -- puppet/face/node/install* *err: Try 'puppet help help help' for usage* First step is seeing if puppet will run for you. Puppet runs as root or you need to sudo and run it. What version of puppet are you running? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Passing http_proxy_host option
Hi, I've been trying to pass the http_proxy_host option to puppet but it's not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:p...@fqdn.com.au --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose --http_proxy_host=http://user:p...@fqdn.com.au --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose --http_proxy_host=http://user:p...@fqdn.com.au; --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/default.pp Do I have a problem with my syntax? Can anyone offer me a proper solution for how to successfully pass the http_proxy_host option to puppet? I've checked and the settings dont look like they've taken: # DEBUG # --- vagrant@vagrant-debian-squeeze:~$ puppet --configprint all | grep proxy http_proxy_host = none http_proxy_port = 3128 # --- # INFO # --- vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet puppet/squeeze uptodate 2.6.2-5+squeeze6 puppet-common/squeeze uptodate 2.6.2-5+squeeze6 # --- I should say I originally tried to do this with Vagrant (see here for more info https://groups.google.com/forum/?fromgroups=#!topic/vagrant-up/IW97AZbxdVc ) although I eventually realised I couldn't even do this through puppet so I'm keen on trying to solve both issues. Thanks, Drew. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/pJflxk94Y2kJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passing http_proxy_host option
Also I tried upgrading puppet and got the same results. vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet facter/squeeze uptodate 1.6.12-1puppetlabs2 puppet/squeeze uptodate 2.7.19-1puppetlabs2 puppet-common/squeeze uptodate 2.7.19-1puppetlabs2 puppetlabs-release/squeeze uptodate 1.0-5 On Monday, October 1, 2012 10:18:25 AM UTC+10, drew khoury wrote: Hi, I've been trying to pass the http_proxy_host option to puppet but it's not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:p...@fqdn.com.au --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose --http_proxy_host= http://user:p...@fqdn.com.au --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose --http_proxy_host= http://user:p...@fqdn.com.au; --modulepath '/tmp/vagrant-puppet/modules-0' /tmp/vagrant-puppet/manifests/default.pp Do I have a problem with my syntax? Can anyone offer me a proper solution for how to successfully pass the http_proxy_host option to puppet? I've checked and the settings dont look like they've taken: # DEBUG # --- vagrant@vagrant-debian-squeeze:~$ puppet --configprint all | grep proxy http_proxy_host = none http_proxy_port = 3128 # --- # INFO # --- vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet puppet/squeeze uptodate 2.6.2-5+squeeze6 puppet-common/squeeze uptodate 2.6.2-5+squeeze6 # --- I should say I originally tried to do this with Vagrant (see here for more info https://groups.google.com/forum/?fromgroups=#!topic/vagrant-up/IW97AZbxdVc) although I eventually realised I couldn't even do this through puppet so I'm keen on trying to solve both issues. Thanks, Drew. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/t21ZthYb_YoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Passing http_proxy_host option
On Sun, Sep 30, 2012 at 5:36 PM, drew khoury drew.kho...@gmail.com wrote: Also I tried upgrading puppet and got the same results. vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet facter/squeeze uptodate 1.6.12-1puppetlabs2 puppet/squeeze uptodate 2.7.19-1puppetlabs2 puppet-common/squeeze uptodate 2.7.19-1puppetlabs2 puppetlabs-release/squeeze uptodate 1.0-5 Try setting it in puppet.conf and with export http_proxy= like in this thread: http://projects.puppetlabs.com/issues/15453 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Passing http_proxy_host option
Setting the env variable manually does work, however I'm trying to run puppet via Vagrant, so I wonder where I have to set the http_proxy variable to get it to work when puppet is loaded via Vagrant. On Monday, October 1, 2012 11:03:25 AM UTC+10, Clarence Beeks wrote: On Sun, Sep 30, 2012 at 5:36 PM, drew khoury drew@gmail.comjavascript: wrote: Also I tried upgrading puppet and got the same results. vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet facter/squeeze uptodate 1.6.12-1puppetlabs2 puppet/squeeze uptodate 2.7.19-1puppetlabs2 puppet-common/squeeze uptodate 2.7.19-1puppetlabs2 puppetlabs-release/squeeze uptodate 1.0-5 Try setting it in puppet.conf and with export http_proxy= like in this thread: http://projects.puppetlabs.com/issues/15453 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/v51_0-Alu6MJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Passing http_proxy_host option
Looks like I was able to get it to work by executing the export command through a bash script, initiated via puppets exec logic in my puppet manifest. Not the most elegant solution but good enough to get me working. I had originally tried setting this in ~/.bashrc but with no luck. Now I'm... - doing a straight export http_proxy=... (in my bash script) as well as... - adding to /home/vagrant/.bashrc This way puppet gets the proxy at runtime if I log in as vagrant I get proxy too. Thanks for pointing me in the right direction! On Monday, October 1, 2012 12:15:23 PM UTC+10, drew khoury wrote: Setting the env variable manually does work, however I'm trying to run puppet via Vagrant, so I wonder where I have to set the http_proxy variable to get it to work when puppet is loaded via Vagrant. On Monday, October 1, 2012 11:03:25 AM UTC+10, Clarence Beeks wrote: On Sun, Sep 30, 2012 at 5:36 PM, drew khoury drew@gmail.com wrote: Also I tried upgrading puppet and got the same results. vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet facter/squeeze uptodate 1.6.12-1puppetlabs2 puppet/squeeze uptodate 2.7.19-1puppetlabs2 puppet-common/squeeze uptodate 2.7.19-1puppetlabs2 puppetlabs-release/squeeze uptodate 1.0-5 Try setting it in puppet.conf and with export http_proxy= like in this thread: http://projects.puppetlabs.com/issues/15453 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/9UtdF2mG5MwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Passing http_proxy_host option
May have spoken too soon. If I set the env variable, and I'm manually logged, then I run puppet all is good. I'm still not clear on how I set the env variable when puppet is invoked from Vagrant (this might end up being a question for Vagrant not puppet?). Setting the env variable in a bash script invoked via the puppet manifest proved to be useless, as it doesn't have any scope OUTSIDE the bash script. I've tried a combination of setting the variable in /home/vagrant/.bashrc AND keeping the env via env_keep in sudoers but I'm not sure I'm understanding how Vagrant is invoking Puppet. On Monday, October 1, 2012 12:30:35 PM UTC+10, drew khoury wrote: Looks like I was able to get it to work by executing the export command through a bash script, initiated via puppets exec logic in my puppet manifest. Not the most elegant solution but good enough to get me working. I had originally tried setting this in ~/.bashrc but with no luck. Now I'm... - doing a straight export http_proxy=... (in my bash script) as well as... - adding to /home/vagrant/.bashrc This way puppet gets the proxy at runtime if I log in as vagrant I get proxy too. Thanks for pointing me in the right direction! On Monday, October 1, 2012 12:15:23 PM UTC+10, drew khoury wrote: Setting the env variable manually does work, however I'm trying to run puppet via Vagrant, so I wonder where I have to set the http_proxy variable to get it to work when puppet is loaded via Vagrant. On Monday, October 1, 2012 11:03:25 AM UTC+10, Clarence Beeks wrote: On Sun, Sep 30, 2012 at 5:36 PM, drew khoury drew@gmail.com wrote: Also I tried upgrading puppet and got the same results. vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo apt-show-versions | grep puppet facter/squeeze uptodate 1.6.12-1puppetlabs2 puppet/squeeze uptodate 2.7.19-1puppetlabs2 puppet-common/squeeze uptodate 2.7.19-1puppetlabs2 puppetlabs-release/squeeze uptodate 1.0-5 Try setting it in puppet.conf and with export http_proxy= like in this thread: http://projects.puppetlabs.com/issues/15453 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/KFY7rL2lVnkJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Solaris Packages for Puppet 3.0.0-rc7, Facter 1.6.0 and Hiera 1.0.0
The ext/ips folder in the main repos contains the necessary incantations. Use rake package:bootstrap at root to pull down the puppet/packaging repo and rake package:ips to build. On Saturday, September 29, 2012 12:41:44 AM UTC-7, Alan Chalmers wrote: Great to see some Solaris IPS love for these. I added these to my local repo went to use them and my only issue I'm running ruby 1.9.3 Any chance you can share your method for rolling these gems up into IPS as I'd prefer to keep with a more recent version of ruby. Cheers alan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ohsh0OWrD1gJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
