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
On Tuesday, February 11, 2014 6:05:54 PM UTC-6, Joaquin Menchaca wrote:
I was wondering is there is a way to see what puppet things a node
resource is, such as classes it includes. Somehow in our environment it is
picking up a class that we did not specify.
I could believe that you are
Is there a way to blow away the cache and refresh? We don't use ENC in
this environment, just a simple site.pp, which references nodes.pp.
Segue, what I like about ENC is that you can call your homegrown script,
get a yaml of params, classes for that node. I wish I could get something
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
