Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v12] Reorganize the config reference #22271

Merged
merged 4 commits into from
Mar 7, 2023
Merged

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Feb 24, 2023

Backport #21594 to branch/v12

@ptgott ptgott enabled auto-merge (squash) February 27, 2023 23:12
@ptgott ptgott force-pushed the bot/backport-21594-branch/v12 branch from 0949742 to c2a41a0 Compare February 27, 2023 23:12
auto-merge was automatically disabled February 28, 2023 20:15

Merge queue setting changed

@ptgott ptgott enabled auto-merge March 2, 2023 22:29
ptgott and others added 3 commits March 7, 2023 16:20
Closes #11253

This change breaks up the config reference by moving each Teleport
service's configuration settings into a separate YAML snippet, and
organizing each YAML snippet into a `TabItem` within a `Tabs` with
`dropdownView` enabled. When Teleport Enterprise Cloud doesn't support a
service, this change adds a `Notice` with a message about Teleport
Enterprise Cloud in the relevant `TabItem`.

I thought this approach would be cleaner than alternatives:

- **Including an H2 for each service:** With this approach, the
  configuration reference would be even longer than it is now. With the
  approach I'm proposing, readers would navigate to "Reference
  configurations", then choose a service from a dropdown menu: much less
  scrolling for slightly more clicking.

- **Including another set of `TabItem`s for Teleport editions:** I
  thought about adding a `Tabs` with a dropdown option for each Teleport
  edition and a horizontal `TabItem` for each service, but this would
  require horizontal scrolling and doesn't scale very well.

- **Including horizontal tabs for each Teleport edition**, with an inner
  dropdown menu for each Teleport service: There is currently no way to
  do this without multiple `Tabs` components, which gets messy quickly.

**Note** that this change does not attempt to copy-edit comments/example
values within the configuration snippets. The scope of this change is
limited only to reorganization.
Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>
@ptgott ptgott force-pushed the bot/backport-21594-branch/v12 branch from c2a41a0 to 5de6fd5 Compare March 7, 2023 21:21
@ptgott ptgott disabled auto-merge March 7, 2023 21:21
Use headings instead of `TabItem`s to split up sections of the config
reference.
@ptgott ptgott force-pushed the bot/backport-21594-branch/v12 branch from 5de6fd5 to 77cda82 Compare March 7, 2023 21:24
@ptgott ptgott enabled auto-merge March 7, 2023 21:25
@ptgott ptgott added this pull request to the merge queue Mar 7, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 7, 2023
@ptgott ptgott added this pull request to the merge queue Mar 7, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 7, 2023
@ptgott ptgott added this pull request to the merge queue Mar 7, 2023
Merged via the queue into branch/v12 with commit 2a0c881 Mar 7, 2023
@github-actions github-actions bot deleted the bot/backport-21594-branch/v12 branch March 7, 2023 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants