MVD Deploy workflow can fail as the Azure resource naming is not unique across repository forks/branches.
Sample run on MVD main repository with error message "The storage account named mvd83dataspacedid is already taken" and "The storage account named mvd83gaiaxdid is already taken".
cloud-cd.yaml indicates:
# Update this value with a unique name to guarantee uniqueness of resource names and avoid conflicts between fork repositories when running CD workflow.
# CD workflow creates resources with this prefix and destroy them.
env:
CD_RESOURCES_PREFIX: mvd
But it seems this is not enough to prevent all kinds of clashes
Acceptance Criteria
[x] Investigate cause for the name clash
[x] Implement a solution to prevent clashes in forks
Feature TBD
Description
MVD Deploy workflow can fail as the Azure resource naming is not unique across repository forks/branches.
Sample run on MVD main repository with error message "The storage account named mvd83dataspacedid is already taken" and "The storage account named mvd83gaiaxdid is already taken".
cloud-cd.yaml indicates:
But it seems this is not enough to prevent all kinds of clashes
Acceptance Criteria
Tasks