Epic Goal:

https://github.com/vmware-tanzu/velero/blob/82111093fe0a11b7693705f35341a16ac19e9220/design/biav2-design.md

https://github.com/vmware-tanzu/velero/blob/23c69f46abb7174f715fc8b526a70aed47ce2d14/design/general-progress-monitoring.md

Why is this important?

• Allow for BIA Execute() to optionally initiate a long-running operation and report on operation status.

Scenarios:

•   Several long running B/R's

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Test coverage for the new features must be verified

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
  For QE- 1 - Regression tests, All the existing tests should pass for datamover, 2 - Parallel backup new test for async data mover. 3 - performance test cases

• DOC - Downstream documentation merged: <link to meaningful PR>