-
Story
-
Resolution: Unresolved
-
Normal
-
ACM 2.14.0
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
-
-
-
None
Value Statement
Ensure the issue title clearly reflects the value of this spike story.
(Explain the "WHY")
Determine and investigate making the APIs available and more simple rather than manually adding them as an Admin for 2.15
These APIs https://github.com/stolostron/multicloud-operators-foundation/blob/main/docs/clusterview/clusterview.md#kubevirtprojectsclusterviewopen-cluster-managementio-api are needed to have permission for some VM actions a user can take in the ACM vm workflow.
Slack Thread https://redhat-internal.slack.com/archives/C08V08S4WMV/p1749585740234479
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- is triggered by
-
ACM-20193 Scenario Testing for Fine Grained RBAC
-
- Closed
-