Azure / data-management-zone

Template to deploy the Data Management Zone of Cloud Scale Analytics (former Enterprise-Scale Analytics). The Data Management Zone provides data governance and management capabilities for the data platform of an organization.
MIT License
169 stars 87 forks source link

Bug: Global service non-unique names cause deployment errors #289

Open lostdoco opened 2 years ago

lostdoco commented 2 years ago

Deployment Mode

Azure DevOps

Steps to reproduce

Deploy as per the instructions in /docs/DataManagementAnalytics-AzureDevOpsDeployment.md prefix = "dmz" environment = "dev"

Two ways to fix this

  1. use bicep unique string function (eg, uniqueString(subscription().subscriptionId)) instead of prefix and static names
  2. allow enterprise users to provide name params for each sub object so they can maintain their naming conventions

Error Message

{
    "status": "Failed",
    "error": {
        "code": "InvalidTemplateDeployment",
        "message": "The template deployment 'purview001' is not valid according to the validation procedure. The tracking id is '3b29a72d-f899-4a83-b44e-4c7dc0d60af6'. See inner errors for details.",
        "details": [
            {
                "code": "1006",
                "message": "Account dmz-dev-purview001 name is invalid or already exists please choose new name"
            }
        ]
    }
}

{
    "status": "Failed",
    "error": {
        "code": "VaultAlreadyExists",
        "message": "The vault name 'dmz-dev-vault001' is already in use. Vault names are globaly unique so it is possible that the name is already taken. If you are sure that the vault name was not taken then it is possible that a vault with the same name was recently deleted but not purged after being placed in a recoverable state. If the vault is in a recoverable state then the vault will need to be purged before reusing the name. For more information on soft delete and purging a vault follow this link https://go.microsoft.com/fwlink/?linkid=2147740."
    }
}

{
    "status": "Failed",
    "error": {
        "code": "AlreadyInUse",
        "message": "The registry DNS name dmzdevcontainerregistry001.azurecr.io is already in use. You can check if the name is already claimed using following API: https://docs.microsoft.com/en-us/rest/api/containerregistry/registries/checknameavailability"
    }
}

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n  \"error\": {\r\n    \"code\": \"AlreadyInUse\",\r\n    \"message\": \"The registry DNS name dmzdevcontainerregistry001.azurecr.io is already in use. You can check if the name is already claimed using following API: https://docs.microsoft.com/en-us/rest/api/containerregistry/registries/checknameavailability\"\r\n  },\r\n  \"status\": \"Failed\"\r\n}"}]}

Screenshots

No response

Code of Conduct