Expose TLS setup in /api/tls #4224
Closed
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
mmatur
added
status/1-needs-design-review
area/api
area/tls
and removed
status/0-needs-triage
labels
|
I'm fighting with tls configuration. I need some explicit certificates, some star certificates, and an ACME fallback. But now, I'm fighting with some client side crash. I'm seeking some visibility. |
|
This PR goes in the wrong direction. I'll be back with a demo : https://github.com/factorysh/demo_traefik_cfssl. |
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?
This PR add an entrypoint in the api for exposing tels configs.
Motivation
It's hard to understand troubles with https. I want to see what is done, not what I asked.
More