-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
docs/consul: rename the Vault secret engine for Consul integration #20049
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general this change looks good to me, but there's an inconsistency throughout.
The path changes between consul-kv/secret/
and consul-kv/data/secret
. Both between pages and within a single page.
Is that intended? It's difficult for me to tell whether you're intentionally creating these split paths for secrets management or if it's a typo.
There's a similar issue on an enterpriselicense
path and a license
path.
Approving so you're not blocked.
website/content/docs/k8s/deployment-configurations/vault/data-integration/bootstrap-token.mdx
Show resolved
Hide resolved
website/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx
Outdated
Show resolved
Hide resolved
website/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx
Outdated
Show resolved
Hide resolved
…integration/index.mdx Co-authored-by: Jeff Boruszak <[email protected]>
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
2 similar comments
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
…tegration into release/1.17.x (#20092) docs/consul: rename the Vault secret engine for Consul integration (#20049) * rename the KV secret engine * update WAN federation guide * update snapshot-agent doc * update replication doc * update partition doc * update gossip doc * update ent-license doc * update bootstrap-token doc * update index doc * fix license kv path * vault kv path explanation for /data/ * Update website/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx --------- Co-authored-by: Jeff Boruszak <[email protected]>
…tegration into release/1.16.x (#20093) docs/consul: rename the Vault secret engine for Consul integration (#20049) * rename the KV secret engine * update WAN federation guide * update snapshot-agent doc * update replication doc * update partition doc * update gossip doc * update ent-license doc * update bootstrap-token doc * update index doc * fix license kv path * vault kv path explanation for /data/ * Update website/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx --------- Co-authored-by: Jeff Boruszak <[email protected]>
…tegration into release/1.15.x (#20094) docs/consul: rename the Vault secret engine for Consul integration (#20049) * rename the KV secret engine * update WAN federation guide * update snapshot-agent doc * update replication doc * update partition doc * update gossip doc * update ent-license doc * update bootstrap-token doc * update index doc * fix license kv path * vault kv path explanation for /data/ * Update website/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx --------- Co-authored-by: Jeff Boruszak <[email protected]>
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
19 similar comments
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@krastin, a backport is missing for this PR [20049] for versions [1.15,1.16,1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
…20049) * rename the KV secret engine * update WAN federation guide * update snapshot-agent doc * update replication doc * update partition doc * update gossip doc * update ent-license doc * update bootstrap-token doc * update index doc * fix license kv path * vault kv path explanation for /data/ * Update website/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx Co-authored-by: Jeff Boruszak <[email protected]> --------- Co-authored-by: Jeff Boruszak <[email protected]>
Description
There was feedback from our Support team about customers facing an issue following the documentation from the Vault for Consul: System integration into the Vault for Consul: Data integration. The former defines a
consul
-named Vault secret engine, but the latter runs commands and config against asecrets
-named Vault secret engine - no doubt a leftover from times where the default secret engine from running Vault in-dev
mode was used to showcase functionality in the docs.Furthermore, because of the secret engine name
consul
, the customers were confused and expected the secret engine to be of the Consul type and not the KV type.With that in mind, this PR changes the docs in the following way:
consul-kv
secrets
is being used for all token-related configuration so that in Production environments, that specific path can be allowed/disallowed read/write access easier for separate admin and non-admin user roles.Testing & Reproduction steps
N/A
Links
Related Docs: Vault as the Secrets Backend (K8s)
PR Checklist