Open rudfoss opened 5 years ago
@panchagnula Hey Sisira, would you mind taking a look at this issue? If this should be redirected to the ARM team, please let me know and I'll reassign accordingly.
@Nking92 , not sure if there is a known issue with passing cloningInfo in an ARM Template with slot.
The overwrite flag is currently not working properly, which is why you're getting a conflict. We'll try to get that fixed soon. Sorry for the inconvenience.
No problem. Thanks for looking into this!
no update on this? still seeing this issue.
@Nking92 is this fixed now? can you please update this issue?
@Nking92 I am getting the issue for one of my customers who is using ARM template for deployment. I did reproduce the issue at my end. Do we have an ETA when is this going to be fixed?
@naveedaz for me to follow-up with on this.
I have the same issue... Any solution?
no solution as yet - this is a backend bug so moving to the right GitHub alias
Is there any update in regards to this issue?
this issue seems already fixed
Is this issue ever going to be fixed? It is impossible to redeploy a template when using cloningInfo unless you know ahead of time if the resource already exists and set the overwrite property accordingly. This goes against the whole premise of ARM.
Description
I'm trying to deploy a web app with two slots (production, deploytarget). Everything works fine the first time, but subsequent runs with the web app already present fail with an error indicating the site already exists. I was under the impression that ARM templates should always be able to run even if the resources already exist? If not is there a quick way to tell ARM that it should not touch the slot if it exists?
The problem goes away if I remove the "cloningInfo" options from the template. It appears there is a problem with cloning onto an existing app service.
Script/Steps for Reproduction
This is the template that is used:
Module Version
Environment Data
Debug Output