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

Dynamic configuration #754

Closed
nivekuil opened this issue Apr 18, 2022 · 2 comments
Closed

Dynamic configuration #754

nivekuil opened this issue Apr 18, 2022 · 2 comments

Comments

@nivekuil
Copy link

Feature Request

I am writing a consul fleetlock server and want to configure zincati's update strategy dynamically depending on whether the server is running on the host. Currently it seems like the only time zincati reads the config is when it restarts but this is a little hard to pull off from a container. It would be nice if zincati watched the config directories or if I could send a reload command somehow.

@cgwalters
Copy link
Member

I think from a privileged container you can systemctl restart zincati.

@lucab
Copy link
Contributor

lucab commented Apr 19, 2022

Thanks for the report. Yes, configuration reloading (i.e. graceful agent reset) is a missing feature which could be added to Zincati. The idea is that this should be exposed through the DBus interface. This request is already tracked in #673, thus I'm closing this duplicate ticket.

However for your specific usecase I think that @cgwalters's suggestion is a good one: systemctl restart zincati goes through DBus as well, so you'll need a privileged container either for interacting with systemd or for interacting with Zincati. At that point, a full service restart is likely a better option.

@lucab lucab closed this as completed Apr 19, 2022
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

3 participants