[v9] Edit Database Access guides for Cloud users #11846
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
r0mant
approved these changes
Apr 11, 2022
ptgott
force-pushed
the
paul.gottschling/11668-bp-v9
branch
from
4b98e28 to
1adc967
Compare
Backports #11668 * Edit Database Access guides for Cloud users This edits Database Access guides that show you how to access specific databases. These guides follow the same structure and use the same partials, so it made sense to address them in a single commit. See #10637 Edits made - Some Prerequisites sections were either absent or required "Teleport," which I've clarified with a scoped Tabs component to indicate the appropriate client tools for each deployment type. Since we instruct users on deploying the Auth/Proxy later in the guide, I restricted this to client tools. Also flesh out the Prerequisites a bit in general. - Add ScopedBlocks for minor details that vary between scopes. - Ensure that all commands that take place on the Database Service node are described correctly as taking place on that node. - Change the tctl-auth-sign.mdx partial. Since the start-auth-proxy.mdx partial now instructs self-hosted users to run tctl commands on the Auth Service host, we no longer need the Self-Hosted tab. As a result, I have turned the Cloud tab into a ScopedBlock. - Reorder self-hosted guide sections so users start the Auth/Proxy before running "tctl auth sign". Otherwise, this command will not work. - Minor style/grammar tweaks * Respond to PR feedback
ptgott
force-pushed
the
paul.gottschling/11668-bp-v9
branch
from
1adc967 to
e379afc
Compare
Closed
Closed
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.
Backports #11668
This edits Database Access guides that show you how to access
specific databases. These guides follow the same structure and use the
same partials, so it made sense to address them in a single commit.
See #10637
Edits made
Some Prerequisites sections were either absent or required
"Teleport," which I've clarified with a scoped Tabs component to
indicate the appropriate client tools for each deployment type.
Since we instruct users on deploying the Auth/Proxy later in the
guide, I restricted this to client tools. Also flesh out the
Prerequisites a bit in general.
Add ScopedBlocks for minor details that vary between scopes.
Ensure that all commands that take place on the Database Service node
are described correctly as taking place on that node.
Change the tctl-auth-sign.mdx partial. Since the start-auth-proxy.mdx
partial now instructs self-hosted users to run tctl commands on the
Auth Service host, we no longer need the Self-Hosted tab. As a result,
I have turned the Cloud tab into a ScopedBlock.
Reorder self-hosted guide sections so users start the Auth/Proxy
before running "tctl auth sign". Otherwise, this command will not
work.
Minor style/grammar tweaks