Skip to content
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.

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

Implement dynamic reloading of allowlist / blocklist permissions without full restarting of bridge #78

Open
MurzNN opened this issue May 1, 2021 · 0 comments

Comments

@MurzNN
Copy link

MurzNN commented May 1, 2021

On my setups I have the script, that dynamically manage allowlist / blocklist (named now as whitelist / blacklist in config file) of users, that can access bridge. But the problem is that for apply changes I need to do a full restart of bridge.

At now permissions are managed via provisioning.whitelist and provisioning.blacklist sections of main config.yaml file.

The restart itself is not a problem, but the problem is that all users receive "reconnected" messages on all their puppets each time when I change permissions policy, that is too noisy for other users. Also at restart time bridge can lose some messages, I guess.

So will be good to implement any way to dynamically reload of permission rules, without restarting of bridge and reconnecting of puppets for users, whose permissions are not changed.

And maybe good idea is to store user permissions info separately from main config file, maybe even in database?

@MurzNN MurzNN changed the title Implement dynamic reloading of whitelist / blacklist permissions without full restarting of bridge Implement dynamic reloading of allowlist / blocklist permissions without full restarting of bridge May 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant