[VAULT-34482] UI: Update Namespace Picker #29995
Closed
Conversation
This file contains hidden or 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
github-actions
bot
added
the
hashicorp-contributed-pr
|
CI Results: |
beagins
force-pushed
the
VAULT-34482/namespace-picker
branch
2 times, most recently
from
cc432f2 to
7448316
Compare
* docs: Update Seal/Unseal concept topic * docs: Edits * docs: Edits * docs: Edits * docs: Edits * docs: Edits * docs: Edits * Additional edits * Remove unnecessary sentence --------- Co-authored-by: Yoko Hyakuna <[email protected]>
* move sync activation and capabilities from flag service to version service and components * cleanup unnecessary args * remove permissions service * un-nest (some) modules * simplify overview test so logic is easier to follow * modal test * update service tests * change back to 403 because maybe it is permissions related? * fix tests running on CE * small cleanup * fix logic based on feedback * add logic for hvd specifically, update cluster tests
…ers were overriding the WIF configuration (#29982)
* generates new api client version with runtime changes for VoidResponse type and JSONApiResponse transformer update * removes extractData middleware from api service * converts tools/unwrap component to ts and updates to use api service * another api client version with more tweaks to JSONApiResponse in runtime * removes extractData test for api service
* Update the callout note for accuracy * Change the callout type from warning to tip * Format fixes * Minor title update
beagins
force-pushed
the
VAULT-34482/namespace-picker
branch
from
7448316 to
067008e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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
main)Outstanding items that will be addressed in separate PRs before the feature sidebranch is merged to main:
Screenshots
TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.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.