Value Statement

As an ACM policy user, I need to specify a maximum time to wait for the policy compliance before failing the rollout so that policies that check status have time to become compliant. I also need the ability to move on with the rollout regardless.

Note that this should work generically so that even the "All" rollout strategy will leverage this.

Definition of Done for Engineering Story Owner (Checklist)

• A new field of "spec.rolloutStrategy.maxSucceededWait" is added in the format of {"time": "5m", "timeoutFailsRollout": true}

  .

• Not setting this will result in the existing behavior of waiting for the policy to become compliant forever.
• If this timeout happens, rolloutStatus is "Failed" for timeoutFailsRollout=true and "Timeout" for timeoutFailsRollout=false.

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.