Skip to content

Satisfy the messaging linter #24603

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.

Sign up for GitHub

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

Merged
ptgott merged 1 commit into from
Apr 18, 2023
Merged

Satisfy the messaging linter #24603

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,5 @@
title: Teleport Changelog
description: The Changelog provides a comprehensive description of the changes introduced by each Teleport release.
---

{/*lint disable messaging*/}
(!CHANGELOG.md!)
4 changes: 2 additions & 2 deletions docs/pages/desktop-access/active-directory-manual.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ following [Getting Started with Windows Access](getting-started.mdx).
Continue with this guide if:

- You're running an older version of Teleport and can't upgrade.
- You want to install Desktop Access using the same instance of `teleport`
- You want to install the Desktop Service using the same instance of `teleport`
running the Proxy/Auth Services.

</Admonition>
Expand Down Expand Up @@ -495,7 +495,7 @@ the filepath to the `der_ca_file` configuration variable.

<Admonition type="note" title="Teleport CA">
Prior to v8.0, the Teleport CA was not compatible with Windows logins. If
you're setting up Desktop Access in an existing cluster created before v8.0,
you're setting up the Desktop Service in an existing cluster created before v8.0,
you must first perform a [CA rotation](../management/operations/ca-rotation.mdx) in
order to resolve this.
</Admonition>
Expand Down