nagios-nrpe role does not define it's own sudo rights #77
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: evolix/ansible-roles#77
Loading…
Reference in New Issue
No description provided.
Delete Branch "nagios-sudoers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Based on the discussion in #49
I'm creating a new pull request since this is planned for buster.
I approve this idea. We should have a round of discussion with the rest of the team to verify that there is no hidden issue with that.
Can we merge this now or are we still waiting on somebody's input ?
LGTM
I'm not fully comfortable with that PR in it's current state.
First because it's not targeting a specific release of Debian. We don't want to apply this to Jessie and Stretch. If we target buster, that would require "fixing" all buster (as we want uniformity). Otherwise I'd wait for Bullseye.
Second, I think we need to be more careful with that change as we could be in situations where no sudo commands are defined for nagios, or defined in both files (Side note: If it's defined two files, will it work ? or break sudo config ?)
I’m not fully comfortable with that PR in it’s current state.
First because it’s not targeting a specific release of Debian. We don’t want to apply this to Jessie and Stretch. If we target buster, that would require “fixing” all buster (as we want uniformity). Otherwise I’d wait for Bullseye.
Second, I think we need to be more careful with that change as we could be in situations where no sudo commands are defined for nagios, or defined in both files (Side note: If it’s defined two files, will it work ? or break sudo config ?)
I'm not full comfortable with that. I've explained in depth with my message in the PR discussion
I was initially told that we should wait for buster to merge this. Now we're talking about waiting for bullseye ? Nobody thought to check if we had any buster stuff to merge before starting to deploy buster machines, how is this not going to happen again for bullseye ?
Pull request closed