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

Support live reload of configuration #73

Open
andygrunwald opened this issue Mar 24, 2017 · 0 comments
Open

Support live reload of configuration #73

andygrunwald opened this issue Mar 24, 2017 · 0 comments

Comments

@andygrunwald
Copy link
Contributor

Configs should be reloadable by some kind of unix signal or by socket communication (mini protocol).
The modification part should be done by calling Configure() again. Plugins will have to react accordingly.

Server part:

  • Password protected (provided via command line parameter, SHA512 encoded)
  • Add plugin: id + config
  • Remove plugin: id
  • Modify plugin config: id + config
  • Reset all (like signal part)

Signal part:

  • Use any not-yet-used signal like SIGUSR
  • Create a diff between current state and config loaded
  • Add new plugins
  • Reconfigure existing plugins
  • Remove all plugins not existing in new config
  • Start new producers
  • Start new consumers

Important: This is just an idea and this ticket can be used for a discussion. You have ideas? Feel free to add them here. You have concerns? Add a comment! Or maybe you have an idea how to develop it? Feel free to run a prototype.

For this feature, the architecture change that is coming in v0.5 is required.

@arnecls arnecls added this to the v0.5.0 milestone Mar 27, 2017
@arnecls arnecls removed this from the v0.5.0 milestone May 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants