-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
UI Hide Secrets Sync from nav if not on license and/or no policy permissions #27262
Merged
Monkeychip
merged 24 commits into
main
from
ui/VAULT-27608/hide-secrets-sync-when-no-access
Jun 11, 2024
Merged
Changes from 1 commit
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
64c2fd0
intial changes, haven't tested client counts or done test coverage
Monkeychip 931a926
client count rename getter to clairfy
Monkeychip ac6b262
fix has-permission api-paths
Monkeychip b1ad18f
wip
Monkeychip 09162c4
wip
Monkeychip e67076e
fix: explicitly refresh vault.cluster model to re-fetch activatedFeat…
e69075b
tests: fix # of assertions for verifying that activation was called
27df01a
tests: tidy overview-test
7fc2fd7
add additional api permission path and move fetch back to application
Monkeychip 36fbb78
add test coverage for the service
Monkeychip 1f2a88b
Merge branch 'main' into ui/VAULT-27608/hide-secrets-sync-when-no-access
Monkeychip 462d258
cleanup
Monkeychip 9f1ab09
remove test that checked for upsell without license or on community
Monkeychip e4e1080
small comment change
Monkeychip 3ec1646
welp missed component getter
Monkeychip 628ea6b
flaky test fix
Monkeychip dccc476
flaky test
Monkeychip 22ce68a
small nit changes from pr reviews
Monkeychip 6fd9b21
add defaults to sync mirage handler
Monkeychip 51bf477
Gate sync overview route for users without access (#27320)
e6b9811
Merge branch 'main' into ui/VAULT-27608/hide-secrets-sync-when-no-access
Monkeychip 8f0fed0
add type enterprise required now because we do a check for this first
Monkeychip 0e598d8
Merge branch 'main' into ui/VAULT-27608/hide-secrets-sync-when-no-access
Monkeychip e8bf2c4
fix oss test
Monkeychip File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
you can probably take this or leave it, but i tried explicitly passing in the parent route that we want refreshed here to see if it'd help us assert that the get activated features was successfully re-fetched. i tried this based on the docs i read here:
doing this works fine in the UI, and after adding a bunch of
console.log
statements i can see even in the test output that _/activation-flags
is fetched after a POST, but i can't get the assertions working how i'd like. because we have these assertions that effectively test that the UI updates once the feature is activated i think we're safe skipping the extra assertions.