-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels