feat: new permission to manage integration #7162
Merged
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
JedrzejJanasiak
force-pushed
the
apim-4415-integration-permissions
branch
from
3716e2b
to
ae56adc
Compare
jgiovaresco
approved these changes
Apr 5, 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.
Issue
https://gravitee.atlassian.net/browse/APIM-4415
Description
This is subtask for story: https://gravitee.atlassian.net/browse/APIM-4236
It contains changes required to enable managing permissions for performing CRUD operations on integrations
Additional context
Some part of the code like new EnvironmentPermission and RolePermission was added in previous PR. (#6991)
This pr is more about attaching this permissions to certain users and allowing access for integration endpoint only with new permissions granted