-
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: instant updates #27668
Merged
Merged
docs/vso: instant updates #27668
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CI Results: |
Build Results: |
benashz
reviewed
Jul 12, 2024
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.
Looks good. I have a few comments and suggestions.
benashz
approved these changes
Jul 17, 2024
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.
Looks great! Nice work!
Monkeychip
pushed a commit
that referenced
this pull request
Jul 24, 2024
benashz
pushed a commit
that referenced
this pull request
Jan 8, 2025
benashz
added a commit
that referenced
this pull request
Jan 10, 2025
* 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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
hashicorp-contributed-pr
If the PR is HashiCorp (i.e. not-community) contributed
pr/no-changelog
pr/no-milestone
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds documentation for enabling instant updates with Vault Enterprise and VSO, to go along with the implementation in hashicorp/vault-secrets-operator#771
Associated RFC: https://go.hashi.co/rfc/vlt-320
PR preview links:
TODO only if you're a HashiCorp employee
getting backported to N-2, use the new style
backport/ent/x.x.x+ent
labelsinstead of the old style
backport/x.x.x
labels.the normal
backport/x.x.x
label (there should be only 1).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.