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

deployment keys: disable service if no key destinations are in /run/ #1057

Merged
merged 1 commit into from Apr 20, 2019

Conversation

jslight90
Copy link
Contributor

@jslight90 jslight90 commented Nov 27, 2018

The nixops-keys service only needs to be enabled if the destination of one or more keys is a volatile directory (/run/).

This was causing an issue for me with the nixpkgs httpd (apache2) module. Said module creates a systemd service dependent on keys.target. I don't use deployment keys with httpd, but I do have other nixops modules with deployment keys whose destinations are non-volatile (not in /run/). When restarting the server locally (not with nixops), the nixops-keys service just waits for /run/keys/done to be created, so httpd won't start. In order to start httpd, I have to use nixops to resend the keys that the system already has.

@jslight90
Copy link
Contributor Author

jslight90 commented Nov 27, 2018

I removed the usage of lib as it is already included by with lib at the top of the file.

@AmineChikhaoui AmineChikhaoui merged commit f5d8a4b into NixOS:master Apr 20, 2019
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

Successfully merging this pull request may close these issues.

None yet

3 participants