OADP-6141: Use of kopia from downstream fork

[mpryc]

Use of downstream fork of the Kopia repository.

Similar PR for the downstream velero project: openshift/velero#384

Note:
Before this PR downstream kopia repository was updated:

• In the migtools/kopia repository a new branch was created from the master: master-before-making-konveyor-dev-obsolete
• The master branch was synced from the konveyor-dev (they are now the same)
• The master branch was made default branch, so we have similar naming there to be in sync with oadp-operator

NONE of this affected oadp-1.5 branch:

• oadp-1.5 branch of migtools/kopia repository is the same as konveyor-dev and now the default master
• oadp-1.5 branch of the oadp-operator project still points to the upstream project-velero/kopia from the branch v0.19.0-velero-patch
• The upstream project-velero/kopia from the branch v0.19.0-velero-patch is the same as the master/konveoyr-dev/oadp-1.5 branches from the migtools/kopia repository.

Why the changes were made

Fix: OADP-6141

How to test the changes made

Check the go.mod it should point to migtools/kopia.

[openshift-ci-robot]

@mpryc: This pull request references OADP-6141 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

In response to this:

Use of downstream fork of the Kopia repository.

Note:
Before this PR downstream kopia repository was updated:

• In the migtools/kopia repository a new branch was created from the master: master-before-making-konveyor-dev-obsolete
• The master branch was synced from the konveyor-dev (they are now the same)
• The master branch was made default branch, so we have similar naming there to be in sync with oadp-operator

NONE of this affected oadp-1.5 branch:

• oadp-1.5 branch of migtools/kopia repository is the same as konveyor-dev and now the default master
• oadp-1.5 branch of the oadp-operator project still points to the upstream project-velero/kopia from the branch v0.19.0-velero-patch
• The upstream project-velero/kopia from the branch v0.19.0-velero-patch is the same as the master/konveoyr-dev/oadp-1.5 branches from the migtools/kopia repository.

Why the changes were made

Fix: OADP-6141

How to test the changes made

Check the go.mod it should point to migtools/kopia.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@mpryc: This pull request references OADP-6141 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

In response to this:

Use of downstream fork of the Kopia repository.

Note:
Before this PR downstream kopia repository was updated:

• In the migtools/kopia repository a new branch was created from the master: master-before-making-konveyor-dev-obsolete
• The master branch was synced from the konveyor-dev (they are now the same)
• The master branch was made default branch, so we have similar naming there to be in sync with oadp-operator

NONE of this affected oadp-1.5 branch:

• oadp-1.5 branch of migtools/kopia repository is the same as konveyor-dev and now the default master
• oadp-1.5 branch of the oadp-operator project still points to the upstream project-velero/kopia from the branch v0.19.0-velero-patch
• The upstream project-velero/kopia from the branch v0.19.0-velero-patch is the same as the master/konveoyr-dev/oadp-1.5 branches from the migtools/kopia repository.

Why the changes were made

Fix: OADP-6141

How to test the changes made

Check the go.mod it should point to migtools/kopia.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpryc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mpryc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@mpryc: This pull request references OADP-6141 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

In response to this:

Use of downstream fork of the Kopia repository.

Similar PR for the downstream velero project: openshift/velero#384

Note:
Before this PR downstream kopia repository was updated:

• In the migtools/kopia repository a new branch was created from the master: master-before-making-konveyor-dev-obsolete
• The master branch was synced from the konveyor-dev (they are now the same)
• The master branch was made default branch, so we have similar naming there to be in sync with oadp-operator

NONE of this affected oadp-1.5 branch:

• oadp-1.5 branch of migtools/kopia repository is the same as konveyor-dev and now the default master
• oadp-1.5 branch of the oadp-operator project still points to the upstream project-velero/kopia from the branch v0.19.0-velero-patch
• The upstream project-velero/kopia from the branch v0.19.0-velero-patch is the same as the master/konveoyr-dev/oadp-1.5 branches from the migtools/kopia repository.

Why the changes were made

Fix: OADP-6141

How to test the changes made

Check the go.mod it should point to migtools/kopia.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@mpryc: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.