Merged
Conversation
…ndow and the agent will honor it. Per configuration.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are many pieces of software that require restarts to consume updated TLS/SSL certificates. Often times those restarts are not side-effect free. Users may get booted, services may be temporarily unavailable etc. To accommodate scenarios where you can't just update certificates any old time, we're now allowing the specification of a "deploy window" in an agent configuration. You can specify a time range (local to the box) that the update can occur - and you can pick which days of the week this range is valid for.
Looks like this in the CertKit app:
