Alex Frankel

Only Resource Group scoped deployments support `Mode`, so the issue is not that the command is missing a parameter set, but that the functionality at those deployments scopes does not...

You cannot mix and match deployment modes in the way you describe. Because the subscription must be deployed with `incremental` mode, so do all the other linked/nested deployments.

We recognize it is not the ideal situation, which is why we are focused on getting Deployment Stacks out. That will effectively support Complete Mode at all scopes. @settrend --...

>That said, a Bicep deployment run, moreover, should be able to remove redundant resources. The delete functionality you are describing is exactly how Deployment Stacks is expected to behave. There...

One thing to add is the Bicep VS Code extension supports "rename symbol" so you should only have to rename each identifier once and bicep will update all the uses...

Good find - we allow this in bicep, so we shouldn't change this when decompiling. Out of curiosity - are you using that script to stage non-template artifacts like a...

Got it. It looks like the bicep/template code does not need anything other than bicep/template code in order to execute. For example, you don't have a resource that requires a...

Given we already have some cases where customers are hitting the 4MB limit, I am not particularly concerned with making the problem worse. I would optimize for enabling the functionality...

Can you provide a correlation ID for this issue to help us investigate?

Connected to #6206