feat(bulk-import): add if predicate gating - #4687
Conversation
|
Important This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior. Changed Packages
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4687 +/- ##
=======================================
Coverage 62.72% 62.72%
=======================================
Files 2636 2636
Lines 105422 105422
Branches 29526 29513 -13
=======================================
Hits 66125 66125
Misses 37458 37458
Partials 1839 1839
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
507c9eb to
50d83b9
Compare
|
It looks like permission is disabled in the app config that the tests use. The test cases that check if bulk import is denied are not working, since there is no call to |
de7d573 to
b8f9c2d
Compare
Signed-off-by: Debsmita Santra <debsmita.santra@gmail.com>
b8f9c2d to
91fed90
Compare
|



Hey, I just made a Pull Request!
Resolves:
https://redhat.atlassian.net/browse/RHIDP-15542
Solution description:
bulk.importfrom resource permission (resourceType: 'bulk-import') to a feature-level BasicPermission with empty attributes, matching how authorization is actually enforced today.AddRepositoriesPagein the NFS flow; legacy (./legacy) still uses usePermission in BulkImportSidebarItem and shows a denied alert on direct navigation.Note: The previous resource permission provided no real resource-level authorization (every resourceRef was "bulk-import", no conditional rules, no getResources). It also blocked adoption of the NFS if predicate for conditional UI registration. The new model aligns permission definition, RBAC policy (bulk.import, use, allow), backend checks, and NFS visibility.
Screenshot:
✔️ Checklist