{"action":"opened","issue":{"url":"https://api.github.com/repos/curationexperts/hydra-ubuntu/issues/5","labels_url":"https://api.github.com/repos/curationexperts/hydra-ubuntu/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/curationexperts/hydra-ubuntu/issues/5/comments","events_url":"https://api.github.com/repos/curationexperts/hydra-ubuntu/issues/5/events","html_url":"https://github.com/curationexperts/hydra-ubuntu/issues/5","id":117436316,"number":5,"title":"Questions","user":{"login":"mark-dce","id":3064318,"avatar_url":"https://avatars.githubusercontent.com/u/3064318?v=3","gravatar_id":"","url":"https://api.github.com/users/mark-dce","html_url":"https://github.com/mark-dce","followers_url":"https://api.github.com/users/mark-dce/followers","following_url":"https://api.github.com/users/mark-dce/following{/other_user}","gists_url":"https://api.github.com/users/mark-dce/gists{/gist_id}","starred_url":"https://api.github.com/users/mark-dce/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mark-dce/subscriptions","organizations_url":"https://api.github.com/users/mark-dce/orgs","repos_url":"https://api.github.com/users/mark-dce/repos","events_url":"https://api.github.com/users/mark-dce/events{/privacy}","received_events_url":"https://api.github.com/users/mark-dce/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-17T19:54:53Z","updated_at":"2015-11-17T19:54:53Z","closed_at":null,"body":"- [ ] is it better to run become/sudo at the playbook level or have it at the task level? - @mark-dce thinks it's easier for folks new to the scripts to figure out exactly what's going on if the elevated privilege is set explicitly at the individual task level.  It might also be slightly more secure to set become at the task level that at the whole role level.\r\n- [ ] what playbooks should be in the repo?   Should project level playbook like goldenseal or adrl live in their own repo?\r\n- [ ] how do we go about making roles idempotent\r\n- [ ] how do we go about DRYing up the codebase - identical tasks live under both housekeeping roles, some variables are declared in two or three different places - it's hard to tell which takes precedence in a particular playbook\r\n- [ ] do we need group_vars?  All of our use cases are for single server targets, so it seems like we might be able to just put variables defaults in the appropriate role and overrides in the main playbook.  The more general version of this might be \"is there a consistent way we can set up defaults and override them?\""}}