Separate role access restrictions for catalog items #22573
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.
Closes #22421
Previously user role access restriction for Catalog Items, Orchestration
Stacks, Key Pairs, Services, VMs, and Templates were set with a single
control (vm_restriction).
Break out the ability to set access restriction for catalog items
separately from other types.
This feature is useful when an administrator wants to give a group
access to a catalog item (service_template) but wants any services
ordered to be restricted to the individual users.
Corresponding PRs: