8000 Define user/group per script · Issue #295 · evrardjp/ansible-keepalived · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Define user/group per script #295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Salvoxia opened this issue Feb 19, 2025 · 0 comments
Open

Define user/group per script #295

Salvoxia opened this issue Feb 19, 2025 · 0 comments

Comments

@Salvoxia
Copy link
Salvoxia commented Feb 19, 2025 •
edited
Loading

Hi,

I'm using check and notify scripts with this role. The check script certainly is ok with running with restricted permissions, but the notify scripts do require root user.
So I'm looking to configure root user for the notify scripts only, as described in the keepalived config documentation:

# to MASTER transition
 notify_master /path/to/master.sh [username [groupname]]

However, when specifying my notify_master script that way

notify_master: /path/to/master.sh root

the role generates the following configuration in keepalived.conf:

notify_master "/path/to/master.sh root"

Of course the role cannot distinguish between a script argument and a user definition, so now it created a script with file name /path/to/master.sh root, while the script itself is running as keepalived_script.

Am I missing something or is this not possible with the role at the moment?
If the latter, I'd be happy to provide a PR for implementing it.

Best Regards
Salvoxia
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Salvoxia
0