Rancher deploy hook both for deploy and renew #1531
+273
−0
Conversation
This file contains 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
Add a rancher deploy-hook script that functions both for initial certificate deployment and for updating them when renewed For this purpose we store the rancher configuration from certificate deployments within the acme.sh domain configuration file
|
The check seems to have failed due to a libc6 dependency error. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a second attempt (see #1348) at managing rancher certificates via acme.sh deploy hook, this time both for initial deployment and updates when certificates are renewed. Rancher details are stored in acme's domain configuration files.
The script comments contains documentation for users on how to use this deploy hook to achieve both goals.