Fix to allow actions on the network if it belongs to a project#9550
Fix to allow actions on the network if it belongs to a project#9550DaanHoogland merged 1 commit intoapache:mainfrom
Conversation
|
@blueorangutan package |
|
@harikrishna-patnala a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9550 +/- ##
==========================================
Coverage 15.54% 15.54%
- Complexity 11995 11997 +2
==========================================
Files 5499 5499
Lines 481706 481706
Branches 58660 58852 +192
==========================================
+ Hits 74879 74884 +5
+ Misses 398541 398535 -6
- Partials 8286 8287 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10703 |
DaanHoogland
left a comment
There was a problem hiding this comment.
clgtm, but wonder if this covours all basis (viewers of a project that have a view only role in the project for instance)
vladimirpetrov
left a comment
There was a problem hiding this comment.
LGTM based on manual testing using the steps provided in the PR description. Tested before and after the patch.
Description
This PR fixes the issue #9413
The original fix was to allow user to do actions (update, restart, delete) on the network only if the user owns the network and if user role is of Admin or domain admin.
If the network belongs to a project then the actions can be allowed as it belongs to only to that project.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
Before fix with a network in project

After fix with a network in project

How Has This Been Tested?