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

Update create-a-replication-token.mdx #21073

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SuyashHashiCorp
Copy link

While testing the changes in my labs, found out one wrong command. Instead of "consul set-agent-token" it will be "consul acl set-agent-token".

Description

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

While testing the changes in my labs, found out one wrong command. Instead of "consul set-agent-token" it will be "consul acl set-agent-token".
@SuyashHashiCorp SuyashHashiCorp requested a review from a team as a code owner May 9, 2024 13:54
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@github-actions github-actions bot added the type/docs Documentation needs to be created/updated/clarified label May 9, 2024
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

Copy link
Member

@blake blake left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this.

@blake blake added pr/no-changelog PR does not need a corresponding .changelog entry backport-inactive/1.16 This release series is no longer active backport-inactive/1.17 This release series is no longer active. Use backport/ent/1.17. backport/1.18 labels May 9, 2024
@zalimeni zalimeni added backport/1.18 Changes are backported to 1.18 and removed backport/ent/1.18 labels May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.18 Changes are backported to 1.18 backport-inactive/1.16 This release series is no longer active backport-inactive/1.17 This release series is no longer active. Use backport/ent/1.17. pr/no-changelog PR does not need a corresponding .changelog entry type/docs Documentation needs to be created/updated/clarified
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants