Fail to deploy via ARM Template

[Vivihung]

Love love love the ARM support in instruction! While creating resources from the custom template, notice strange default values in Location and Storage Account Name. Is it expected?

[Vivihung]

If I use the variable-like default values and deploy without changing anything, got deployment error

Raw error (I removed my subscription id and resource group name from the error.)

{
  "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": "InvalidTemplate",
      "message": "Unable to process template language expressions for resource '/subscriptions/<subscription_id>/resourceGroups/<rg_name>/providers/Microsoft.Resources/deploymentScripts/deploymentScript' at line '93' and column '5'. 'The template parameter 'errorDocument404Contents' is not found. Please see https://aka.ms/arm-template/#parameters for usage details.'"
    }
  ]
}

[luisquintanilla]

Thanks. I'll take a look. I thought I removed that parameter requirement but I'll double check.

[Vivihung]

Thanks, @luisquintanilla. I'm less worried about the weird parameter value since I can trigger deployment. I'm more concerned about the deployment failure. Did we miss to provide the value of errorDocument404Contents somewhere in the custom template? Can you repro the deployment error?

[luisquintanilla]

@Vivihung The issue is I had removed the option to provide an error document contents in the Azure Portal UI, but it was still one of the params used during deployment. Should be fixed by #7 . Let me know if you still have issues.

Re: the weird regex looking items, they are supposed to look like that. For the location, it gets replaced with the location of the resource group the storage account is being created in and for name, it gets replaced by a string which is the concatenated strings "stor" and the value of the resource group ID. This is done to ensure uniqueness and also automate the deployment. The user always has the option of course of replacing these with their own, but it's recommended to leave all the defaults as is.

[Vivihung]

Confirm the deployment works now. Thanks!