You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I was wondering, since this repo is using hiera_include in order to classify a node with it respective role and following the recomendation in a role-profile architecture for "one role-one node", what would be the solution when one defines a role for a node in the nodeSpecific hierarchy level, but there are already other role defined in the typeSpecific hierarchy level. This will cause hiera to apply more than one role to the node. This is an issue i'm facing right now. Currently looking for a way to mimic hiera_include that would do priority lookup but this is a long shot for me. Any suggestion?
Hierarchy:
-nodeSpecific
-typeSpecific
-common
The text was updated successfully, but these errors were encountered:
It's really up to you if you adhere to the one role, one node guideline, and if you do, it's also your job to make sure you don't assign it in two places. To that extent, I only assign roles in the puppet_role hierarchy in this repo.
It's also worth noting that it is a guideline and one you should only follow if it makes sense for you.
Hi,
I was wondering, since this repo is using hiera_include in order to classify a node with it respective role and following the recomendation in a role-profile architecture for "one role-one node", what would be the solution when one defines a role for a node in the nodeSpecific hierarchy level, but there are already other role defined in the typeSpecific hierarchy level. This will cause hiera to apply more than one role to the node. This is an issue i'm facing right now. Currently looking for a way to mimic hiera_include that would do priority lookup but this is a long shot for me. Any suggestion?
Hierarchy:
-nodeSpecific
-typeSpecific
-common
The text was updated successfully, but these errors were encountered: