Skip to content

Backport of Updated Nomad Secret Engine docs with proper terminology into release/1.9.x#16860

Closed
hc-github-team-secure-vault-core wants to merge 1 commit into
release/1.9.xfrom
backport/docs/nomad-secrets-engine/violently-correct-chigger
Closed

Backport of Updated Nomad Secret Engine docs with proper terminology into release/1.9.x#16860
hc-github-team-secure-vault-core wants to merge 1 commit into
release/1.9.xfrom
backport/docs/nomad-secrets-engine/violently-correct-chigger

Conversation

@hc-github-team-secure-vault-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #16859 to be assessed for backporting due to the inclusion of the label backport/1.9.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


This PR accomplishes what PR 8983 meant to do.

Since PR 8983 was opened back in 2020, it's troublesome to merge the PR. We'll fix the terminology with this PR and close PR 8983.


Overview of commits

@hashicorp-cla
Copy link
Copy Markdown

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


temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

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

@yhyakuna yhyakuna closed this Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants