docs: MySQL secrets clarification#24931
Merged
alexfornuto merged 1 commit intomasterfrom Apr 20, 2023
Merged
Conversation
zmb3
approved these changes
Apr 20, 2023
ptgott
approved these changes
Apr 20, 2023
|
@alexfornuto See the table below for backport results.
|
This was referenced Apr 21, 2023
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
3 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.
Closes #12790
Since this issue was created we've standardized our prerequisites section for all database docs to clarify that
tctlis run locally after authenticating withtshto the Teleport cluster. This PR addresses and remaining confusion around wheretctlis run when creating secrets for MySQL, and where the secrets need to ultimately go.