Modify ACME configuration migration into KV store #2598
Merged
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
This was referenced Dec 20, 2017
This was referenced Dec 21, 2017
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.
What does this PR do?
During Træfik configuration migration (from file to KV store (thanks to the
storeconfigsubcommand)), ACME configuration is not correctly initialized ifstorageFileis not provided.Træfik can not start in this case!
The PR allows initializing correctly all the KV store keys needed by ACME during
storeconfigprocess, even ifstorageFileis not provided.The PR allows deleting automatically the key
/traefik/acme/storagefilefrom KV stores when ACME configuration is migrated. This key has to be deleted because :Motivation
Fixes #927, #2547, #1283, #2581
More
Additional Notes