New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error downloading the template #8288
Comments
Interestingly, we just found that if you refresh the page after being redirected to the error as described, you will be presented with another screen with a "Select a template" tab. There is a dropdown on that page and if you search for "sas" you will see "sas-viya" ... if you select that template you will be presented with the list of parameters as expected. |
I also get this error since today, and it probably affects all templates. |
I agree @Yvand , I documented in my notes that it should always be this (at least until something changes and it’s not): My previous notes from my previous deployment has the same URI that @tarastclair mentioned: |
Hey @Yvand and @tarastclai, this seems to be working as expected now. |
Nope, I just tested and I keep getting the error on all the templates (I tested 4 randomly). |
ACOM had a bug - I think it's been fixed now |
Thanks for confirming... |
I am getting this error for a template in another repro (Azure/Azure-Sentinel) |
@DeanGross do you mean https://azure.microsoft.com/en-us/resources/templates/azure-sentinel/ ? |
Currently I faced this same issue, My steps
|
Azure Quickstart
Issue Details
Automatically redirected to an error when attempting to deploy (was not happening last week). Error is:
There was an error downloading the template from URI 'https://github.com/Azure/azure-quickstart-templates/blob/master/sas-viya/azuredeploy.json'. Ensure that the template is publicly accessible and that the publisher has enabled CORS policy on the endpoint. To deploy this template, download the template manually and paste the contents in the 'Build your own template in the editor' option below.
Repro steps
The text was updated successfully, but these errors were encountered: