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

Feature: Implement scheduled deployment #329

Open
webprofusion-chrisc opened this Issue Jun 18, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@webprofusion-chrisc
Copy link
Contributor

webprofusion-chrisc commented Jun 18, 2018

While a certificate can generally be renewed at any time, the updated certificate file (or stored cert) may not actually be applied until a service restarts (such as Apache, MS Remote Desktop Gateway etc).

Ideally a user should be able to specify when to deploy a renewed certificate:

  • Time of day
  • Day of Week/Month

This would effectively be the post-request stage of the renewal process, including the post-request scripting (if any). This would require determining how to handle certificate stored before deployment (is it applied to the certificate store already?) and UI to specify target date/time preferences.

This overall concept is that many users will have a 'maintenance window' where they can tolerate service restarts etc. The assumption is that this would only take place if the certificate renewal has already succeeded (as a renewal can take multiple attempts and must tolerate failure, whereas deployment is generally expected to only happen once per renewed certificate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment