Skip to content

[v13] Edit forScopes configurations and edit guides#28742

Merged
ptgott merged 1 commit into
branch/v13from
paul.gottschling/28443-bp-v13
Jul 14, 2023
Merged

[v13] Edit forScopes configurations and edit guides#28742
ptgott merged 1 commit into
branch/v13from
paul.gottschling/28443-bp-v13

Conversation

@ptgott
Copy link
Copy Markdown
Contributor

@ptgott ptgott commented Jul 5, 2023

Backports #28443

  • Edit forScopes configurations and edit guides

Closes #26500

This change requires merging gravitational/docs#326 to add a Team scope to the docs.

This updates pages within the docs so that:

  • Each page's forScopes configuration is accurate, especially with regard to support for Teleport Team.
  • All scoped components match the forScopes configuration for each page. For this, I used the linter introduced by Lint alignment of components with forScopes docs#327.
  • Respond to alexfornuto feedback

@ptgott ptgott marked this pull request as draft July 6, 2023 20:56
@ptgott

This comment was marked as outdated.

@ptgott ptgott force-pushed the paul.gottschling/28443-bp-v13 branch 2 times, most recently from c398a0d to 83e7a33 Compare July 7, 2023 18:45
@ptgott ptgott marked this pull request as ready for review July 7, 2023 18:45
@github-actions github-actions Bot requested a review from stevenGravy July 7, 2023 18:46
</TabItem>
<TabItem scope={["cloud"]}
label="Teleport Cloud">
label="Teleport Enterprise Cloud">
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ptgott Should this remain just "Cloud" for instructions that apply to both Team and Enterprise Cloud, and have the commercial prereqs partial for when only Enterprise Cloud applies?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I created the original PR, I assumed that Team wouldn't require the Enterprise tctl client, so I made a separate tab. If Team does require Enterprise tctl, though, I think we can use "Teleport Team/Enterprise Cloud" as the label and use the same tab item for both Team and Enterprise Cloud.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've confirmed that teams users should use enterprise tctl.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've backported #29024 into this PR

@ptgott ptgott requested a review from alexfornuto July 7, 2023 22:17
@ptgott ptgott force-pushed the paul.gottschling/28443-bp-v13 branch from 83e7a33 to e77986e Compare July 13, 2023 20:58
Backports #28443

* Edit forScopes configurations and edit guides

Closes #26500

This change requires merging gravitational/docs#326 to add a Team scope
to the docs.

This updates pages within the docs so that:

- Each page's `forScopes` configuration is accurate, especially with
  regard to support for Teleport Team.
- All scoped components match the `forScopes` configuration for each
  page. For this, I used the linter introduced by
  gravitational/docs#327.

* Respond to alexfornuto feedback
@ptgott ptgott force-pushed the paul.gottschling/28443-bp-v13 branch from e77986e to 267d31b Compare July 13, 2023 21:02
@ptgott ptgott added this pull request to the merge queue Jul 14, 2023
Merged via the queue into branch/v13 with commit 7b3eb78 Jul 14, 2023
@ptgott ptgott deleted the paul.gottschling/28443-bp-v13 branch July 14, 2023 18:04
@r0mant r0mant mentioned this pull request Jul 14, 2023
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