This issue is still unresolved as of 3.1.0
# hiera -h resources -c /etc/puppet/hiera.yaml
{webapplication2={Consumer=undef},
webapplication={Consumer={2a=nil, 1a={offset=3},
3a=undef}, indexer=nil}}
hieranil.pp
$fullhash = hiera_hash(resources)
To: puppet-users@googlegroups.com
Sent: Thursday, February 14, 2013 9:15:38 AM
Subject: Re: [Puppet Users] Hiera Questions: Virtual User Resources and Hiera
This issue is still unresolved as of 3.1.0
# hiera -h resources -c /etc/puppet/hiera.yaml
{webapplication2={Consumer=undef
I would make facts on the nodes for these. Let say $role and $subrole
and then just use those in your hierarchy with %{role} and %{subrole}
thus allowing you to set variable for all those machines there.
As far as I understood puppet is a config management system that configures
This thought crossed our minds as well.
I created the following feature request awhile back:
https://projects.puppetlabs.com/issues/13934#change-60706
the intent behind which is if this fact is flagged as immutable, and it
changes, something is drastically wrong… (don't)? do something
until
On Thu, Jun 28, 2012 at 08:04:09PM +0100, R.I.Pienaar wrote:
I would make facts on the nodes for these. Let say $role and $subrole
and then just use those in your hierarchy with %{role} and %{subrole}
thus allowing you to set variable for all those machines there.
Howdy:
I was wondering
On 02. juli 2012 17:26, Darryl Wisneski wrote:
modules I can use hiera to call up my hash and create ruby/puppet
functions to do the server host location and functional logic based
on the default facter facts of hostname and operatingsystem reported
by the server host themselves. All the
On 02. juli 2012 17:26, Darryl Wisneski wrote:
Regards,
-dkw
Ouch, sorry Darryl, I hit the wrong button and posted what I thought of
as a private very quick reply to you .. right on the list.
Now at least everyone sees my honest-to-god thoughts on the matter. And
the scope of the
On Mon, Jul 02, 2012 at 10:13:51PM +0200, Jan Ivar Beddari wrote:
On 02. juli 2012 17:26, Darryl Wisneski wrote:
Regards,
-dkw
Ouch, sorry Darryl, I hit the wrong button and posted what I thought of
as a private very quick reply to you .. right on the list.
Jan:
I too am sorry I
In regard to: Re: [Puppet Users] hiera questions, llow...@oreillyauto.com...:
On Thursday, June 28, 2012 2:04:09 PM UTC-5, R.I. Pienaar wrote:
- Original Message -
I would make facts on the nodes for these. Let say $role and $subrole
and then just use those in your hierarchy
I'm starting to use hiera more, to try to clean up and better modularize
some of our stuff.
I know you can use various facts (such as $::hostname) when defining the
hierarchy and where to look.
We have a few variables that are set based on patterns of hostname, and
currently we have a
On Thursday, June 28, 2012 2:04:09 PM UTC-5, R.I. Pienaar wrote:
- Original Message -
I would make facts on the nodes for these. Let say $role and $subrole
and then just use those in your hierarchy with %{role} and %{subrole}
thus allowing you to set variable for all those
You need your custom fact script in:
module/lib/facter/script
On 29/06/2012, at 7:37, llow...@oreillyauto.com llow...@oreillyauto.com
wrote:
On Thursday, June 28, 2012 2:04:09 PM UTC-5, R.I. Pienaar wrote:
- Original Message -
I would make facts on the nodes for these.
On 22/05/12 00:22, Jeff McCune wrote:
On Mon, May 21, 2012 at 1:24 AM, Luke Bigum luke.bi...@lmax.com
mailto:luke.bi...@lmax.com wrote:
I agree with Gary, Dan, it's probably the lack of data in the
'v_ingroups' key in your YAML that create_resources() is
complaining about. If it
I found an answer to this particular issue. Thanks for the reminder so I can
share the answer:
I found the hiera/yaml way to indicate an empty array !
So, to use my earlier example:
users:
beast:
username : beast
uid :
ingroups :
- ''
info :
On Tuesday, May 22, 2012, Dan White wrote:
I found an answer to this particular issue. Thanks for the reminder so I
can share the answer:
I found the hiera/yaml way to indicate an empty array !
So, to use my earlier example:
users:
beast:
username : beast
uid :
On 18/05/12 14:00, Dan White wrote:
Thanks for responding, Luke.
This looks like a useful expansion of the hiera back-end, but as I am still
fairly new to Puppet (and Python and Ruby for that matter), I think I will wait
for this to be formally accepted and incorporated before trying it
On Mon, May 21, 2012 at 1:24 AM, Luke Bigum luke.bi...@lmax.com wrote:
I agree with Gary, Dan, it's probably the lack of data in the
'v_ingroups' key in your YAML that create_resources() is complaining about.
If it truly can't pass an empty key/val pair you could do something hacky
like use
On 18/05/12 04:04, Dan White wrote:
In a posting a few days ago was this hiera.yaml source listing:
-
:backends: - json
:hierarchy: - %{fqdn}
- %{lmax_role}_role
- %{lmax_env}_server
- %{pop}.tradefair
-
- Gary Larizza g...@puppetlabs.com wrote:
On Thu, May 17, 2012 at 9:12 PM, Dan White y...@comcast.net wrote:
One way I have seen for setting up system users is to create them
virtually and then realize them with the spaceship operator, say by ggroup
-- like this:
User | groups ==
On 18/05/12 13:46, Dan White wrote:
Ah, Gary ! Just the brain I wish to pick ! :)
Thanks for the response. It makes sense.
However, if I perceive this properly, it would provide an All-Or-Nothing
implementation of users.
I am looking for for a way to have a master list of users in hiera and
- Luke Bigum luke.bi...@lmax.com wrote:
On 18/05/12 04:04, Dan White wrote:
In a posting a few days ago was this hiera.yaml source listing:
-
:backends: - json
:hierarchy: - %{fqdn}
- %{lmax_role}_role
-
- Luke Bigum luke.bi...@lmax.com wrote:
On 18/05/12 13:46, Dan White wrote:
Ah, Gary ! Just the brain I wish to pick ! :)
Thanks for the response. It makes sense.
However, if I perceive this properly, it would provide an All-Or-Nothing
implementation of users.
I am looking
On Friday, May 18, 2012, jcbollinger wrote:
On May 17, 11:16 pm, Gary Larizza g...@puppetlabs.com javascript:;
wrote:
That's exactly what I was suggesting. If you declared the users as
create_resources expected it, and included the same user in multiple
levels
of the hierarchy, the
- Luke Bigum luke.bi...@lmax.com wrote:
On 18/05/12 13:46, Dan White wrote:
Ah, Gary ! Just the brain I wish to pick ! :)
Thanks for the response. It makes sense.
However, if I perceive this properly, it would provide an All-Or-Nothing
implementation of users.
I am looking
I wonder if the nil value is not being accepted as 'being passed' - can you
populate the nil value and try again?
On Fri, May 18, 2012 at 2:41 PM, Dan White y...@comcast.net wrote:
- Luke Bigum luke.bi...@lmax.com wrote:
On 18/05/12 13:46, Dan White wrote:
Ah, Gary ! Just the brain
In a posting a few days ago was this hiera.yaml source listing:
-
:backends: - json
:hierarchy: - %{fqdn}
- %{lmax_role}_role
- %{lmax_env}_server
- %{pop}.tradefair
- common
:json:
:datadir: -
One way I have seen for setting up system users is to create them virtually and
then realize them with the spaceship operator, say by ggroup -- like this:
User | groups == 'wheel' |
Reference:
http://www.mail-archive.com/puppet-users@googlegroups.com/msg29719.html
In the referenced posting,
On Thu, May 17, 2012 at 9:12 PM, Dan White y...@comcast.net wrote:
One way I have seen for setting up system users is to create them
virtually and then realize them with the spaceship operator, say by ggroup
-- like this:
User | groups == 'wheel' |
Reference:
28 matches
Mail list logo
