Break up /database-access/guides/ #38574
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
github-actions
bot
requested review from
r0mant,
smallinsky,
xinding33 and
zmb3
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
🤖 Vercel preview here: https://docs-hn46rsek9-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
0d12e00 to
03fe43e
Compare
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
🤖 Vercel preview here: https://docs-1uwfgsnev-goteleport.vercel.app/docs/ver/preview |
ptgott
added
no-changelog
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
03fe43e to
16858b3
Compare
|
🤖 Vercel preview here: https://docs-oj7fh78gk-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
16858b3 to
838d49c
Compare
|
🤖 Vercel preview here: https://docs-pnc0y6iy3-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
838d49c to
23c9c23
Compare
|
🤖 Vercel preview here: https://docs-ps2k4yejd-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
23c9c23 to
df9e1c7
Compare
|
🤖 Vercel preview here: https://docs-fmt6rvjvv-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
df9e1c7 to
93c8cb1
Compare
|
🤖 Vercel preview here: https://docs-m621s1v6k-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
c12ed31 to
d33c455
Compare
Closes #17641 Organize the guides to enrolling databases in specific cloud providers (or self-hosted databases) into separate subsections of the "Database Actions" section, organized by cloud provider (or self-hosted). We can later add general information to the index page of each subsection about how Teleport database access works for each cloud provider. The remaining guides in the "Guides" subsection have to do with database-agnostic functionality of the Teleport Database Service. This change also adds a redirect for each page it moves.
- In the "Database Access" intro page, move the self-hosted section first in the list of links to database-specific guides so it's less easy to miss. - Change "AWS" to "Amazon" in product names.
This prevents us from running into Vercel route limit issues, since the number of redirects is large.
ptgott
force-pushed
the
paul.gottschling/17641-db-org
branch
from
d33c455 to
2aadb4c
Compare
|
🤖 Vercel preview here: https://docs-pphx58ch2-goteleport.vercel.app/docs/ver/preview |
ptgott
added a commit
that referenced
this pull request
May 15, 2024
Backports #38574 * Break up /database-access/guides/ Closes #17641 Organize the guides to enrolling databases in specific cloud providers (or self-hosted databases) into separate subsections of the "Database Actions" section, organized by cloud provider (or self-hosted). We can later add general information to the index page of each subsection about how Teleport database access works for each cloud provider. The remaining guides in the "Guides" subsection have to do with database-agnostic functionality of the Teleport Database Service. This change also adds a redirect for each page it moves. * Respond to greedy52 feedback - In the "Database Access" intro page, move the self-hosted section first in the list of links to database-specific guides so it's less easy to miss. - Change "AWS" to "Amazon" in product names. * Fix linter issues * Remove redirects added by the DB guide reorg This prevents us from running into Vercel route limit issues, since the number of redirects is large.
ptgott
added a commit
that referenced
this pull request
May 24, 2024
Backports #38574 * Break up /database-access/guides/ Closes #17641 Organize the guides to enrolling databases in specific cloud providers (or self-hosted databases) into separate subsections of the "Database Actions" section, organized by cloud provider (or self-hosted). We can later add general information to the index page of each subsection about how Teleport database access works for each cloud provider. The remaining guides in the "Guides" subsection have to do with database-agnostic functionality of the Teleport Database Service. This change also adds a redirect for each page it moves. * Respond to greedy52 feedback - In the "Database Access" intro page, move the self-hosted section first in the list of links to database-specific guides so it's less easy to miss. - Change "AWS" to "Amazon" in product names. * Fix linter issues * Remove redirects added by the DB guide reorg This prevents us from running into Vercel route limit issues, since the number of redirects is large.
ptgott
added a commit
that referenced
this pull request
May 29, 2024
Backports #38574 * Break up /database-access/guides/ Closes #17641 Organize the guides to enrolling databases in specific cloud providers (or self-hosted databases) into separate subsections of the "Database Actions" section, organized by cloud provider (or self-hosted). We can later add general information to the index page of each subsection about how Teleport database access works for each cloud provider. The remaining guides in the "Guides" subsection have to do with database-agnostic functionality of the Teleport Database Service. This change also adds a redirect for each page it moves. * Respond to greedy52 feedback - In the "Database Access" intro page, move the self-hosted section first in the list of links to database-specific guides so it's less easy to miss. - Change "AWS" to "Amazon" in product names. * Fix linter issues * Remove redirects added by the DB guide reorg This prevents us from running into Vercel route limit issues, since the number of redirects is large.
github-merge-queue bot
pushed a commit
that referenced
this pull request
May 29, 2024
Backports #38574 * Break up /database-access/guides/ Closes #17641 Organize the guides to enrolling databases in specific cloud providers (or self-hosted databases) into separate subsections of the "Database Actions" section, organized by cloud provider (or self-hosted). We can later add general information to the index page of each subsection about how Teleport database access works for each cloud provider. The remaining guides in the "Guides" subsection have to do with database-agnostic functionality of the Teleport Database Service. This change also adds a redirect for each page it moves. * Respond to greedy52 feedback - In the "Database Access" intro page, move the self-hosted section first in the list of links to database-specific guides so it's less easy to miss. - Change "AWS" to "Amazon" in product names. * Fix linter issues * Remove redirects added by the DB guide reorg This prevents us from running into Vercel route limit issues, since the number of redirects is large.
ptgott
added a commit
that referenced
this pull request
May 30, 2024
Also restore the "Guides" page to the sidebar.
github-actions bot
pushed a commit
that referenced
this pull request
May 30, 2024
Also restore the "Guides" page to the sidebar.
github-actions bot
pushed a commit
that referenced
this pull request
May 30, 2024
Also restore the "Guides" page to the sidebar.
github-merge-queue bot
pushed a commit
that referenced
this pull request
May 31, 2024
Also restore the "Guides" page to the sidebar. Co-authored-by: Paul Gottschling <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
May 31, 2024
Also restore the "Guides" page to the sidebar. Co-authored-by: Paul Gottschling <[email protected]>
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.
Closes #17641
Organize the guides to enrolling databases in specific cloud providers (or self-hosted databases) into separate subsections of the "Database Actions" section, organized by cloud provider (or self-hosted).
We can later add general information to the index page of each subsection about how Teleport database access works for each cloud provider. The remaining guides in the "Guides" subsection have to do with database-agnostic functionality of the Teleport Database Service.
This change also adds a redirect for each page it moves.