I always found it surprising and slightly confusing that exec has an 'environment' attribute, I expected that to be a metaparam that could be applied to any resource to indicate what environment it should belong to (defaulting to the current one). Would get freaky as you could then export resources across environment but there's cases where that could be useful.
How is this discrepancy currently handled in the Nagios types? I know that those types have attributes that clash with metaparams for example, like alias. On Wednesday, 2 April 2014 16:40:59 UTC+2, Ken Barber wrote: > > > I quite like the idea of allowing people to restrict collection based > > on environment. That requires a slight tweak to the puppetdb terminus > > code, but I don't think it'll be too bad. Erik is correct, though, > > that we can't really use "environment" as the search term there > > because there are some resources that use "environment" as a parameter > > name (like "exec"). :/ > > Does anyone have any suggestions for avoiding this conflict? > > ken. > -- 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/8c242664-e585-4754-90cf-e279c9655175%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
