-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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/vso: hvs rotating and dynamic secrets #28656
docs/vso: hvs rotating and dynamic secrets #28656
Conversation
CI Results: |
Build Results: |
…T-30502/vso-hvs-rotating-dynamic
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.
LGTM
secret_name: {"key_one": "value_one", "key_two": "value_two"} | ||
secret_name_key_one: "value_one" | ||
secret_name_key_two: "value_two" |
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.
Nice!
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.
I added one minor nit for your consideration, otherwise +1
|
||
VSO syncs auto-rotating secrets along with static secrets on the | ||
[refreshAfter][hvsa-spec] interval, and rotation is handled by HCP. VSO | ||
syncs dynamic secrets when the [specified percentage](/vault/docs/platform/k8s/vso/api-reference#hvsdynamicsyncconfig) |
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.
nit could we add /vault/docs/platform/k8s/vso/api-reference
to
[va-spec]: /vault/docs/platform/k8s/vso/api-reference#vaultauthspec |
Not sure if there are any other "candidate" paths that we should consider for inclusion as common links.
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.
Do you have an example of how this would work? I'm not finding a way in markdown to define a link to the base url (/vault/docs/platform/k8s/vso/api-reference
) and use that base link along with the anchor (#hvsdynamicsyncconfig
) in the text.
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.
Maybe this one
the [VaultAuth spec][va-spec] for more details. The `VaultAuthGlobal` custom resource is optional and can be used to |
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.
Ah, then I misunderstood. Is the idea to use common-links.mdx
for all VSO links, and not just links that are used on multiple pages? (The links in this PR are only used in a single page, which is why I didn't add them to common-links.)
…T-30502/vso-hvs-rotating-dynamic
Thanks all! Getting this in now so it's up for next week. |
* docs/vso: instant updates (#27668) * Update VSO docs for auto CRD upgrade behaviour (#27763) * VSO: update docs for VaultAuthGlobals (#27797) --------- Co-authored-by: Theron Voran <[email protected]> * Bump VSO versions to 0.8.0 (#27835) * Update VSO docs for v0.8.1 (#27898) * Including missing Helm documentation. * Add version tip for instant updates * Update VSO docs for v0.9.0 (#28639) * Update VSO docs for v0.9.1 (#29151) * vso/docs: restore upgrade instructions (#29159) * docs: Fix path to allowedSprigFuncs (#29026) * docs/vso: fix backwards v1 and v2 links (#28733) Co-authored-by: Theron Voran <[email protected]> * docs/vso: hvs rotating and dynamic secrets (#28656) --------- Co-authored-by: Theron Voran <[email protected]> Co-authored-by: Pascal Hofmann <[email protected]> Co-authored-by: Melody <[email protected]>
Description
Documents usage of HVS rotating and dynamic secrets with VSO, part of VSO v0.9.0.
Preview links:
TODO only if you're a HashiCorp employee
to N, N-1, and N-2, using the
backport/ent/x.x.x+ent
labels. If this PR is in the CE repo, you should only backport to N, using thebackport/x.x.x
label, not the enterprise labels.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.