Skip to content

Edit forScopes configurations and edit guides#28443

Merged
ptgott merged 2 commits into
masterfrom
paul.gottschling/26500-team
Jul 5, 2023
Merged

Edit forScopes configurations and edit guides#28443
ptgott merged 2 commits into
masterfrom
paul.gottschling/26500-team

Conversation

@ptgott
Copy link
Copy Markdown
Contributor

@ptgott ptgott commented Jun 28, 2023

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.

Copy link
Copy Markdown
Contributor

@alexfornuto alexfornuto left a comment

Choose a reason for hiding this comment

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

Recreating this summary post-outage...

I can't say I reviewed every change, but I spot-checked here and there and made a couple notes.

Comment thread docs/config.json Outdated
Comment thread docs/pages/access-controls/guides/hardware-key-support.mdx Outdated
@ptgott ptgott force-pushed the paul.gottschling/26500-team branch 2 times, most recently from 0589cc1 to 627335d Compare June 30, 2023 15:12
@ptgott ptgott force-pushed the paul.gottschling/26500-team branch from 627335d to 6b30c82 Compare June 30, 2023 19:16
@ptgott ptgott enabled auto-merge June 30, 2023 19:16
@ptgott ptgott force-pushed the paul.gottschling/26500-team branch 4 times, most recently from 702dfbb to f5eb310 Compare July 5, 2023 15:24
ptgott added 2 commits July 5, 2023 16:48
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.
@ptgott ptgott force-pushed the paul.gottschling/26500-team branch from f5eb310 to 40ac26a Compare July 5, 2023 20:48
@ptgott ptgott added this pull request to the merge queue Jul 5, 2023
Merged via the queue into master with commit c5ced55 Jul 5, 2023
@ptgott ptgott deleted the paul.gottschling/26500-team branch July 5, 2023 21:16
@public-teleport-github-review-bot
Copy link
Copy Markdown

@ptgott See the table below for backport results.

Branch Result
branch/v11 Failed
branch/v12 Failed
branch/v13 Failed

ptgott added a commit that referenced this pull request Jul 7, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
ptgott added a commit that referenced this pull request Jul 10, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
ptgott added a commit that referenced this pull request Jul 10, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
ravicious pushed a commit that referenced this pull request Jul 11, 2023
* 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 added a commit that referenced this pull request Jul 13, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
ptgott added a commit that referenced this pull request Jul 13, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
github-merge-queue Bot pushed a commit that referenced this pull request Jul 13, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
github-merge-queue Bot pushed a commit that referenced this pull request Jul 14, 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
  gravitational/docs#327.

* Respond to alexfornuto feedback
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.

Add scoped components for Teleport Team

3 participants