On Wednesday, February 12, 2014 4:36:31 PM UTC-6, Joaquin Menchaca wrote: > > Alright, I found the source of my problem, at least I think. The > puppetmaster includes path to modules based on an environment (staging, > production, qa) and a global path shared by all environments. The > deployenv was in both locations, global and the environmental ones. The > module shared by everyone had "import passenger" in it. > > I still wish there was an easy way to generate a list from the site.pp > manifests for debugging, similar to how an ENC can generate a YAML file of > classes/params for the node. >
You can't get a complete listing of all classes declared for a node with anything less than [the equivalent of] a complete catalog compilation. And the catalog emitted by that process contains, in YAML form, details of all class and resource declarations pertinent to the node. If you are using PuppetDB, then it caches the most recently-compiled catalog for each node. You might therefore be able to query its "resources" terminus for the classes declared for your node, relying on the fact that Puppet tends to conflate classes and resources. > What I did was go into /var/lib/puppet/client_data/catalog and looked > at the json file to get some hints. > As I said, the catalog. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users/0a1dfe86-98f8-4a87-a835-b54ed59289dd%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
