Jul 11 2019 06:49 AM - edited Jul 11 2019 06:50 AM
Hi,
In my comprehension :
The first part is deploying infrasctructure in Azure (that make availability set with networks, machines, disks ....), this step is good.
The second part is deploying Managament Tool (to have a SAAS to control infrastructure), in my case i get an error in this part. Through GitHub i deploy in Azure the template and i get a conflit error (see picture), but a web page "Your app service is up and runing") but i don't have managment tool web service.
I'am very disapointed, Somebody can help me.
Thanks
Jul 12 2019 07:02 AM
Jul 15 2019 05:12 AM
Thank you, i posted an issue on GitHub
Jul 19 2019 07:41 AM
@AurelienB
I have opened a ticket in Azure portal and received a hint from Azure Support:
When you use an ARM as in your case, you have to give the name of the Job which should be a unique ID if you follow the documentation:
For each job schedule, the 'name' property is a GUID (Global Unique ID), and this needs to be unique.
In your case, you probably ran it once so it no longer got unique as it got hardcoded.
"[guid(resourceGroup().id, deployment().name)]"
So if the deployment is pushed twice, the job ID might not be unique because the template is used on the same resource group, hence generating the same GUID.
Action Plan:
Jul 23 2019 05:23 AM
I try all this in the next days.
Regards