Shubham Pampattiwar

> Another thing I'm not clear about the design is how BIA/RIA interact with data mover. Is that part will be covered in this PR? @blackpiglet The proposed plugins in...

@blackpiglet +1 to what @sseago is stating. We do not need Velero controlling the async plugin actions currently, as it will add more complications plus there are no uses cases...

/kind changelog-not-required

As discussed, this PR is updated with the first aspects of datamover interface design which have been agreed upon: - Problem Statement - Goals - Non-Goals - Usecases - User...

Totally agree with you @blackpiglet. The datamover implementation details can be worked in a seperate PR. Before that, I would encourage all the interested folks to please review the [Item...

Basically we want a Volume on replication source pod whose `VolumeSource` would be a secret.

@JohnStrunk I am good with design 2 as well, simple and straight forward. But yeah I kind of agree with @tesshuflower that users might be used to setting a file...

@Lyndon-Li Are you talking about instances like these https://github.com/vmware-tanzu/velero-plugin-for-csi/blob/main/internal/backup/pvc_action.go#L92

+1 on what @draghuram is suggesting here.

@abbbi Thank you for the contribution ! Would you please [sign your commit](https://github.com/vmware-tanzu/velero/pull/5348/checks?check_run_id=8367723914) ? And also add a [changelog](https://github.com/vmware-tanzu/velero/actions/runs/3058853612/jobs/4940497915) file ?