-
Story
-
Resolution: Done
-
Undefined
-
ACM 2.11.0
Value Statement
As an operator policy user, I want defaults to be selected like the OpenShift console does (e.g. channel), so that I can install operators without in-depth knowledege of OLM.
Definition of Done for Engineering Story Owner (Checklist)
- All OperatorPolicy fields that are required that can be defaulted such as channel, should be defaulted.
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 documented by
-
ACM-11353 Document "Require minimal fields in the operator policy"
- Closed