{"action":"created","issue":{"url":"https://api.github.com/repos/puppetinabox/controlrepo/issues/77","repository_url":"https://api.github.com/repos/puppetinabox/controlrepo","labels_url":"https://api.github.com/repos/puppetinabox/controlrepo/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/puppetinabox/controlrepo/issues/77/comments","events_url":"https://api.github.com/repos/puppetinabox/controlrepo/issues/77/events","html_url":"https://github.com/puppetinabox/controlrepo/issues/77","id":142498423,"number":77,"title":"hiera_include an role in different hiera levels","user":{"login":"MAXxATTAXx","id":399736,"avatar_url":"https://avatars.githubusercontent.com/u/399736?v=3","gravatar_id":"","url":"https://api.github.com/users/MAXxATTAXx","html_url":"https://github.com/MAXxATTAXx","followers_url":"https://api.github.com/users/MAXxATTAXx/followers","following_url":"https://api.github.com/users/MAXxATTAXx/following{/other_user}","gists_url":"https://api.github.com/users/MAXxATTAXx/gists{/gist_id}","starred_url":"https://api.github.com/users/MAXxATTAXx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MAXxATTAXx/subscriptions","organizations_url":"https://api.github.com/users/MAXxATTAXx/orgs","repos_url":"https://api.github.com/users/MAXxATTAXx/repos","events_url":"https://api.github.com/users/MAXxATTAXx/events{/privacy}","received_events_url":"https://api.github.com/users/MAXxATTAXx/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-21T23:20:43Z","updated_at":"2016-03-22T00:44:54Z","closed_at":null,"body":"Hi,\r\nI 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?\r\n\r\nHierarchy:\r\n-nodeSpecific\r\n-typeSpecific\r\n-common"},"comment":{"url":"https://api.github.com/repos/puppetinabox/controlrepo/issues/comments/199563558","html_url":"https://github.com/puppetinabox/controlrepo/issues/77#issuecomment-199563558","issue_url":"https://api.github.com/repos/puppetinabox/controlrepo/issues/77","id":199563558,"user":{"login":"rnelson0","id":1898351,"avatar_url":"https://avatars.githubusercontent.com/u/1898351?v=3","gravatar_id":"","url":"https://api.github.com/users/rnelson0","html_url":"https://github.com/rnelson0","followers_url":"https://api.github.com/users/rnelson0/followers","following_url":"https://api.github.com/users/rnelson0/following{/other_user}","gists_url":"https://api.github.com/users/rnelson0/gists{/gist_id}","starred_url":"https://api.github.com/users/rnelson0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rnelson0/subscriptions","organizations_url":"https://api.github.com/users/rnelson0/orgs","repos_url":"https://api.github.com/users/rnelson0/repos","events_url":"https://api.github.com/users/rnelson0/events{/privacy}","received_events_url":"https://api.github.com/users/rnelson0/received_events","type":"User","site_admin":false},"created_at":"2016-03-22T00:44:54Z","updated_at":"2016-03-22T00:44:54Z","body":"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.\r\n\r\nIt's also worth noting that it is a guideline and one you should only follow if it makes sense for you."}}