Deployment Issues with Outdated Azure Blob Storage URIs and Missing Storage Keys in Scripts

[np-daxton]

Hello,

I am encountering several issues with the deployment of the "WingtipTicketsSaaS-DbPerTenant" project using both the "Deploy to Azure" button provided in the official documentation and the manual deployment from the GitHub repository. Below are the details of the issues:

1. Missing storageKey in ARM Template: The ARM template lacks the storageKey parameter when deployed through both the "Deploy to Azure" button and manual deployment using the code from the GitHub repository. This omission leads to errors related to invalid storage credentials during the import operation of the .bacpac file. The exact error message encountered in both deployment methods is: "The ImportExport operation failed because of invalid storage credentials."
   
   
   
   
   

2. Inconsistency in storageUri Domain Names: There is a discrepancy in the domain names of the storageUri between the template deployed via the "Deploy to Azure" button and the latest version on GitHub. The domain used by the "Deploy to Azure" is wtdemoresourcestemp.blob.core.windows.net, whereas the GitHub codes uses wingtipsaas1.blob.core.windows.net.
   
   

3. Resource Not Found Error for .bacpac File: Directly accessing the storageUri of the .bacpac file provided in the latest GitHub repository version (https://wingtipsaas1.blob.core.windows.net/bacpacs-dpt/contosoconcerthall.bacpac) results in a "Resource Not Found" error. The error message is as follows:

  <Error>
   <Code>ResourceNotFound</Code>
   <Message>The specified resource does not exist. RequestId:97c12964-f01e-003c-23d9-8fbed1000000 Time:2024-04-16T08:38:33.5851022Z</Message>
   </Error>

These issues are causing significant deployment failures, and it seems that there might be outdated information or errors in the deployment scripts or documentation. Any assistance or updates to resolve these problems would be greatly appreciated.

Thank you.

[faikriza]

I experience the same issue (obvious I guess). Any resolution or workaround that can be applied? Would like to try this out so that i can eventually apply this to my own solution.