Allow users to manage ImageRepository objects with the same access level as Components #194
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
…vel as Components
tkdchen
approved these changes
May 28, 2024
arewm
approved these changes
May 28, 2024
ralphbean
approved these changes
May 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since we are switching to the new way of managing image repositories in Konflux via a separate
ImageRepositopryresource instead ofComponentannotations, we need to grant users permissions to work with the new resource.ImageRepositopryshould be created together with theComponent(by UI) in case user wants to use default image repository option.The permissions are set in sync with the
Componentpermissions of each role.Corresponding permissions change: codeready-toolchain/host-operator#1037