You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per-Backup Storage Location credentials are being introduced in Velero 1.6. These should be tested
Describe the solution you'd like
Have a test that sets up two backup storage locations with different credentials on AWS, Azure and vSphere.
Ensure that backup/restore can occur successfully with both BSLs
Check with Restic and volume snapshots
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
👍 for "The project would be better with this feature added"
👎 for "This feature will not enhance the project in a meaningful way"
The text was updated successfully, but these errors were encountered:
@dsu-igeek Do you think that this can be closed based on the test added in #3559 or would you like to see additional test cases?
The test in that PR allows the creation of another BSL (alongside the default) and can show backup and restore using restic. It does not include volume snapshots though.
Describe the problem/challenge you have
Per-Backup Storage Location credentials are being introduced in Velero 1.6. These should be tested
Describe the solution you'd like
Have a test that sets up two backup storage locations with different credentials on AWS, Azure and vSphere.
Ensure that backup/restore can occur successfully with both BSLs
Check with Restic and volume snapshots
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: