Epic Goal

• The goal for this epic to track the work needed to release the built in Data Mover found in velero v1.12 to OADP tech preview release in 1.3.0
• Why is this important?  The built in Data Mover has less dependencies and the code path is less complex.

• Upstream Design
• Downstream Design ( need pr link )

Scenarios

1. Same as the DM in OADP-1.2.0

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. Velero

Open questions::

1. TBD 

Done Checklist

• [ x ] CI - CI is running, tests are automated and merged.

• [ ] Release Enablement <link to Feature Enablement Presentation>

• [ x ] 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 - 1 - Regression tests, All the existing tests should pass
• [ ] QE - Automated tests merged: <link or reference to automated tests>

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