-
-
Notifications
You must be signed in to change notification settings - Fork 22
Normalize permission model #317
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
Open
emeremikwu-lm
wants to merge
16
commits into
DependencyTrack:main
Choose a base branch
from
emeremikwu-lm:normalize-permission-model
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Normalize permission model #317
emeremikwu-lm
wants to merge
16
commits into
DependencyTrack:main
from
emeremikwu-lm:normalize-permission-model
Conversation
This file contains hidden or 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
Signed-off-by: Emmanuel Meremikwu <[email protected]>
…top level nav components - Updated permission directives to use a more consistent approach with apiserver spec. - Removed unnecessary permission checks and simplified the logic in components such as VulnerabilityAudit, LicenseGroupList, PolicyList, and others. - Enhanced tab management in VulnerabilityAudit.vue by removing redundant data properties and methods. - Streamlined the creation and management of policies and licenses by consolidating permission checks. - Improved the handling of modal visibility and button states based on user permissions. - Cleaned up unused imports and code comments for better maintainability. Signed-off-by: Emmanuel Meremikwu <[email protected]>
…, and VULNERABILITY_ANALYSIS permissions to use PROJECT_READ and FINDING_UPDATE This refactor migrates the usage of the following legacy permissions: - VIEW_POLICY_VIOLATION - VIEW_VULNERABILITY - VULNERABILITY_ANALYSIS and its sub-permissions (CREATE, READ, UPDATE) To (apiserver pr spec.) - PROJECT_READ - FINDING_UPDATE Signed-off-by: Emmanuel Meremikwu <[email protected]>
…ct-related components Signed-off-by: Emmanuel Meremikwu <[email protected]>
…DetailsModal Signed-off-by: Emmanuel Meremikwu <[email protected]>
…ervice and ServiceDetailsModal components Signed-off-by: Emmanuel Meremikwu <[email protected]>
…paration of logic and ehnancements Refactor BToggleableDisplayButton to use v-model for better state management Add AlertListItemDetails component for detailed alert configuration with various input fields and toggles Refactor PolicyListItemDetails to improve project and tag limiting functionality with collapsible sections Enhance PolicyCondition component by simplifying subject selection logic and improving permission handling Signed-off-by: Emmanuel Meremikwu <[email protected]>
…e related components Signed-off-by: Emmanuel Meremikwu <[email protected]>
5fcb0be to
5f4f5a3
Compare
- Introduced `PolicyListDetails.vue` for enhanced policy detail editing with conditions and project/tag limitations. - Added `ProjectPolicyViolationDetails.vue` to display detailed information about policy violations, including comments and analysis options. - Updated `PolicyList.vue` to utilize the new `PolicyListDetails` component for better detail management. - Refactored `FindingAudit.vue` to correct permission directive usage. - Replaced inline detail rendering in `ProjectPolicyViolations.vue` with the new `ProjectPolicyViolationDetails` component for cleaner code and better maintainability. - Adjusted permission checks in `TaggedVulnerabilityListModal.vue` and `VulnerabilityList.vue` for consistency and clarity. Signed-off-by: Emmanuel Meremikwu <[email protected]>
5f4f5a3 to
4dee5e3
Compare
…olved i18n error - Migrated remaining legacysub permissions of permissions (PORTFOLIO_MANAGEMENT) to their appropriate modern counterparts. - Updated and enhanced associated logic to use new permission constants - Improved permission checks and ensured consistency across the codebase. - Cleaned up unused or deprecated permission exports. - resolved i18n 'Inactive' key error Signed-off-by: Emmanuel Meremikwu <[email protected]>
…omponents Signed-off-by: Emmanuel Meremikwu <[email protected]>
9c93fb1 to
77d9efa
Compare
…ion logic. Signed-off-by: Emmanuel Meremikwu <[email protected]>
77d9efa to
0f8b8a1
Compare
Signed-off-by: Emmanuel Meremikwu <[email protected]>
Signed-off-by: Emmanuel Meremikwu <[email protected]>
Signed-off-by: Emmanuel Meremikwu <[email protected]>
Signed-off-by: Emmanuel Meremikwu <[email protected]>
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.
Description
Changes related to Apiserver Normalization PR
Addressed Issue
Additional Details
Checklist