> I'm wondering if it will be possible to disable this behaviour on resource > collections in the terminus? > For us puppet environments are mapped to git branches, and actual > environments (like testing and prod) have different Puppet CAs and PuppetDBs > (it is really best to not mix them anyway). > So it is all right if we record the environment (git branch), but we want to > collect across all of them. And actually this might be useful during a > migration period for others as well, until all nodes have sent in their new > catalogs with environment info.
I think this is a reasonable request, and I think it does provide a mechanism for others to temporarily work around the lack of cross-environment search in the language - a feature that is quite valid, and probably also belongs in the language (ie. collect with an environment == clause for example). Can you update https://tickets.puppetlabs.com/browse/PDB-455 with this idea? I'm working on the code now, it can be easily added so its worth it. > Also, 2.x agents sends their environment as a fact, so for them you could > migrate the data. But not 3.x agents. This actually would have been a great idea (and we could have used this to migrate the catalog), but we're dropping 2.x support in PDB 2.x. It might get some users though ... I'm dithering on whether a ticket should exist for this investigation now. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAE4bNTntT1gnj87Cc5waB6%3DvY13cuy1NBEuurKuiL97eK2MH-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
