> # redefine resources
> mysql_user {
> "frob": ;
> "f...@%": ;
>
> "foo": host => "localhost";
> "f...@localhost": ;
> }
The last pair isn't really a duplicate though, unless you change foo to frob
or frob to foo.
In the following example, I'm using the '@' symbol to indicate that
> $name/$namevar should be built from an array of values inside the 'foo'
> stanza.
>
> foo { @:
> +bar => 'baz',
> +bar2 => 'baz2',
> notakey => 'value'
> }
>
> So, $name would now be "baz_baz2" built from the names prepended with a
> '+'. I suppose you would probably want to sort the values alphabetically
> so that you achieve consistency in your code. Arrays could be handled
> through a concatenation of the values or by spawning additional 'foo'
> resources.
>
The fundamental deference is that David and I are working on a system where,
rather than the namevar being a specific predetermined attribute it would be
be a specific predetermined *set of attributes;* that's the extent of the
change.
What you're describing appears to be having it be an arbitrary, user
determined set of attributes which is way beyond what we're proposing.
Going that far opens a whole case of cans of worms, which we'd rather not.
-- Markus
-----------------------------------------------------------
The power of accurate observation is
commonly called cynicism by those
who have not got it. ~George Bernard Shaw
------------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
