Merge lp:~wesmason/charms/trusty/conn-check/trunk-fix-perms into lp:~ubuntuone-hackers/charms/trusty/conn-check/trunk
Proposed by
Wes Mason
Status: | Merged |
---|---|
Approved by: | Wes Mason |
Approved revision: | 36 |
Merged at revision: | 36 |
Proposed branch: | lp:~wesmason/charms/trusty/conn-check/trunk-fix-perms |
Merge into: | lp:~ubuntuone-hackers/charms/trusty/conn-check/trunk |
Diff against target: |
44 lines (+8/-4) 1 file modified
playbook.yaml (+8/-4) |
To merge this branch: | bzr merge lp:~wesmason/charms/trusty/conn-check/trunk-fix-perms |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Nelson (community) | Approve | ||
Review via email: mp+259102@code.launchpad.net |
Commit message
Ensure config file, if written by charm, is set to the right user/group
Description of the change
Ensure we set the correct user/group on the config file if the charm writes it (rather than being set by config_path).
To post a comment you must log in.
20:48 < noodles> wes: I still don't understand why you don't just do nagios:nagios for those perms?
20:49 < noodles> Why do the "run check" and "run nagios checks" tasks need a separate user?
20:50 < wes> noodles: I don't think they do, although I am uneasy about creating/updating the user in the conn-check charm which may be created/updated differently in the nrpe charm
20:51 -!- noise [<email address hidden>] has quit [Ping timeout: 121 seconds]
20:52 < noodles> wes: why would you create/update the user?
20:52 < noodles> Don't those tasks specifically run after the nagios user will already be created?
20:53 < wes> noodles: nope, as it's not guaranteed you're using nagios with the charm
20:54 < noodles> OK, makes sense.