Epic Goal

• See upstream design at https://github.com/vmware-tanzu/velero/pull/5108/files

Why is this important?

• Enable monitoring of backup/restore item action operations that continue after snapshotting and other operations have completed
• Keep non-usable backups and restores (upload/persistence has not finished, etc.) from appearing as completed
• Make use of plugin API versioning functionality to manage changes to Backup/RestoreItemAction interfaces
• Enable vendors to plug their own data movers into velero using BIA/RIA plugins

Scenarios

1.  Standard B/R 
2.  B/R with data mover

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

Dependencies (internal and external)

1. upstream Velero and associated plugins.

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>
• DOC - Downstream documentation merged: <link to meaningful PR>