Value Statement

As an ACM policy user, I would like to define my clusters in groups for which the policy rollout applies to in order so that I can conservatively rollout the policy.

Definition of Done for Engineering Story Owner (Checklist)

• The policy spec.rolloutStrategy.type field can be set to "ProgressivePerGroup.
• The policy does not rollout if there is more than one placement bound to it. This can be done in a validating webhook or by the ACM hub. Note that the validating webhook would have to exist on Policy and PlacementBinding create/updates.
• The PlacementDecision groups are deployed in order. This excludes support for a "timeout" or "soak time". This is handled separately.
• The placement library should be used for implementing this logic.
• Adding clusters after the rollout completed should result in a "mini" rollout and not roll out all existing clusters. This behavior likely already works using the placement library.

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.