On Dec 14, 2009, at 5:22 PM, Markus Roberts wrote: > Looking at #2813, wherein setting the alias property of a host is also > supposed to set the alias metaparameter of the corresponding resource, > I'm having doubts about the wisdom of letting properties and > metaparameters share pants like that. While it arguably makes sense > in the case of alias, in general this will not be true; there's no > reason to suppose that a type that declares a "schedule" property or a > "before" parameter or whatever would expect values that could be > meaningfully applied to the metaparameters of the same names. > > There are a variety of alternatives: > > * Rename the parameters and disallow such name collisions in general. > * Special case alias (and only alias) to work this way > * Get rid of alias the metaparameter and go to a system where > parameters can be marked as "searchable" and thus function as aliases. > * Something else
As discussed in person, given that it's apparently been confusing to people (according to Dan, people avoid aliases because of this dual functionality), I think we should just rename the parameter. Comments? -- Censorship, like charity, should begin at home; but, unlike charity, it should end there. --Clare Booth Luce --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com -- 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.
