Validate BSL/VSL in E2E tests

[mateusoliveira43]

Today, azure and gcp create non default secrets and do not add that info to SnapshotLocations in DPA, but nevertheless, this test do not break

oadp-operator/tests/e2e/dpa_deployment_suite_test.go

Line 412 in a663e78

Entry("DPA CR with bsl and vsl", InstallCase{

We should validate BSL/VSL in our tests

For consistency, SnapshotLocations build code should be updated to have similar logic to BackupLocations one

oadp-operator/tests/e2e/lib/dpa_helpers.go

Line 82 in a663e78

SnapshotLocations: v.CustomResource.Spec.SnapshotLocations,

oadp-operator/tests/e2e/lib/dpa_helpers.go

Lines 89 to 94 in a663e78

	Credential: &corev1.SecretKeySelector{
	LocalObjectReference: corev1.LocalObjectReference{
	Name: "bsl-cloud-credentials-" + v.Provider,
	},
	Key: "cloud",
	},

Also, this option should be removed also for consistency, as developer can not select BSL secret name for e2e run

oadp-operator/tests/e2e/e2e_suite_test.go

Line 33 in a663e78

flag.StringVar(&credSecretRef, "creds_secret_ref", "cloud-credentials", "Credential secret ref (name) for volume storage location")

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[mateusoliveira43]

/lifecycle frozen