-
Story
-
Resolution: Done
-
Undefined
-
None
-
2
-
False
-
None
-
False
-
ACM-944 - Workload Delivery and Scheduling
-
-
-
GRC Sprint 2023-03, GRC Sprint 2023-04
-
No
Value Statement
As an ACM policy user, I would like to use Placement instead of PlacementRule in the create policy wizard since PlacementRule is being deprecated.
Definition of Done for Engineering Story Owner (Checklist)
- Change the default in the create policy wizard to use Placement instead of PlacementRule. Both are currently supported and will remain so.
- Add a deprecation warning when using PlacementRule as described here:
https://issues.redhat.com/browse/ACM-1114?focusedId=21851634&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21851634
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [x] Unit/function tests have been automated and incorporated into the
build. - [x] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [x] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [x] 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. - [x] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [x] The must-gather script has been updated.
- is depended on by
-
ACM-4911 [QE Automation] Update existing cases to make them compliant with latest placement UI changes
- Closed
- is documented by
-
ACM-5380 PlacementRule deprecation for governance
- Closed
- is related to
-
ACM-3506 Create detail information in the YAML editor to support placement rule deprecation
- Closed
There are no Sub-Tasks for this issue.