> What's the reason for not just requiring full parameter specification, rather than supporting the title short-hand?
The motivating case (file paths, MS Windows vs. *nix, vs. minor players) have the property that not all fields are normally needed for any specific case. We considered the possibility of requiring full specification but some things (e.g. the drive letter on *nix) really are just undef and anything else gets ugly fast. It seems to me we kind of have two problems: How to uniquely specify the > resource with parameters, and how to specify it with a resource reference. > Your solution (the title becomes a template filled in by the different > parameters) does kind of neatly solve it, but I'm afraid it might be too > complicated for normal humans to use. Playing around with it at puppet came we came to the conclusion that, while it could in principle get too complicated to use, in the actual use cases it was dead obvious what was intended--in part because the formats we are wanting to model are themselves extremely well known. > It'd probably be a good idea to run through three or four other resource > types with this to see how it works. E.g., ports (/etc/services), packages > (optionally specify a version number or architecture, where two packages > with the same name but different version/arch are considered different > packages depending on the provider, I think), and probably something else. > We did go through several (ports, mysql users, etc.) though we didn't do the package/arch case. -- 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.
