I really like the metaparameter approach. It's almost self documenting.
On Tuesday, August 5, 2014 6:41:40 PM UTC-7, Reid Vandewiele wrote:
>
> Maybe solving for this use case would be better handled by implementing
> something that looks and feels like a metaparameter rather than trying to
> come up with new syntax. That approach would have the benefit of not
> complicating the language, and meet all of the functional requirements
> discussed so far. It would also be google-able. There would need to be some
> design around the choice of a name for the "metaparameter", but it's easy
> enough to demonstrate the concept with a stand-in like "attribute_defaults"
> or "attribute_hash".
>
> Example 1 (assuming behavior whereinmerging is OK, and that explicit
> parameter specification takes precedence):
>
> apache::vhost { $servername:
> port => $port,
> ssl => $ssl,
> attribute_defaults => $extra_opts,
> }
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/1d38a4dd-596e-4338-b0d5-f6117f3a6052%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
