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 persistent configuration #26

Open
mafik opened this issue Jun 5, 2023 · 0 comments
Open

Support persistent configuration #26

mafik opened this issue Jun 5, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mafik
Copy link
Owner

mafik commented Jun 5, 2023

Many other features in Gatekeeper would need to store some state somewhere. This issue is about adding such mechanism. It should be:

  • familiar (don't invent any new mechanisms or external dependencies)
  • easy to debug by end-users
  • forwards compatible

From the point of Gatekeeper it should support just two methods: Get(key) => value & Set(key, value).

It's ok for the config to be read on start-up only because any changes made by the user would involve restarting / reloading Gatekeeper. To support config reloading, two other features may be implemented as well:

  1. Config validation
  2. Config reloading without service restart

This mechanism may be based on EnvironmentFile= in systemd.

@mafik mafik added this to the 2.0 milestone Jun 11, 2023
@mafik mafik added the enhancement New feature or request label Jun 23, 2023
@mafik mafik removed this from the 2.0 milestone Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant