Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature: Implement scheduled deployment #329
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:
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).