https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • t
    when you say 'to the agent' to mean 'to the box on which i'm running 
    puppet agent -t --environment=testenv
    ?`
  • b
    yes
  • t
    So here's that node's groups:
  • t
    i have two agent-specified envrionments now instead of 1, but that's about it.
  • t
    And note that the node is part of the 
    dev_puppet one-time run exception
    group
  • t
    so its dynamically being added to that group - that's good.
  • s
    hmmm, it’s not a member of any env group which seems strange
  • s
    what does the node group hierarchy look like?
  • t
    its a member of 
    dev_puppet
    which is an env group
  • t
    All Node -> Production Environment -> dev_puppet -> dev_puppet one-time run exception
  • s
    so, your production env group is not a direct child of All Environments?
  • b
    and dev_puppet is under production?
  • s
    mixing classification and env hierarchies is not recommended
  • t
    Its this above
  • b
    wat hc
  • t
    Wow - how bad is it?
  • t
    it's not my fault i swear
  • s
    that is def pretty non standard đŸ˜‰
  • t
    well - i'm certainly interested in making it better, so any recommendations are greatly appreciated.
  • t
    However - I'd also love to know why i can't do the one-off classifications, either
  • s
    out of the box hierarchy looks more like this:
  • s
    and has env groups in a single hierarchy
  • t
    So we have an environment called 
    Production
    for which all other environments are children
  • t
    you're recommending that we have 
    Production
    at the same level as every other environment, in an 
    All Environments
    folder
  • t
    yes?
  • s
    that’s the standard setup that ships out of the box
  • t
    got it
1...464748...73Latest