fix: users can see inaccessible RPs #7707
Merged
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
There was previously no distinction between RPs with no bindings, and RPs that a user did not have access to, as both would appear to have no bindings. As of this PR, if a user does not have access to a workspace that is bound to a resource pool, we should be able to detect it and return a not found error.
Test Plan
using two workspaces (A and B), bind A to a resource pool. create a user with edit access to B, and use the CLI command
det rp bindings list-workspaces <resource pool name>
. You should get an error that the resource pool "does not exist or is not available to view".Commentary (optional)
Checklist
docs/release-notes/
.See Release Note for details.
Ticket