redeploying an Azure App Service ...

[blmiles]

Hello,

I have recently deployed an Azure App Service (includes EF Core) using azd CLI.
I have a Maui App too (also includes EF Core) that uses said service to perform data sync'ing. All works.

This is still only a DEV environment, no need to preserve the Db or data (yet) so no need for migrations yet, either.

I need to make a couple changes to the Db.

If I repeat the deployment of the now existing Azure App Service using the same azd CLI steps, does that over-write that instance with the changes AND update the Db?
OR
Should I delete that Azure App Service with the Db OR the whole resource group and redeploy new?

Is there an azd command that "updates" the targeted deployed Azure App Service instance.

Thanks

[vhvb1989]

Hello @blmiles

If you make changes to your IaC (bicep or terraform files) and then run either azd up or azd provision, azd will run an incremental deployment for your infrastructure. That means any new resources you added will be created but removing resources from your IaC will not make azd to delete them. For updating resources, the deployment will apply the changes when the change is possible. For example, changes the name of a resource might lead to the creation of a new resource (instead of renaming the existing). And there are some changes that can't be applied to some resources after creating them; like changing the consumption model from an App Service might not be possible. For those cases, if the change can't be applied, azd will return a deployment error with some notes about it. You need to manually delete the resource and run azd up or azd provision again to re-create the resource from scratch.

If your changes are only for the service (application code), you can run azd up or azd deploy to reflect those changes by packing and deploying your app to your host in Azure.

[blmiles]

Thanks very much for that feedback!
Most helpful!

Might have further questions once I try things ...

[blmiles]

@vhvb1989 Victor, I've tried both azd up and azd deploy. Both complete successfully.

I added fields to one table in both the Maui App and the Azure App Service code. The Maui app works fine and I can save data into those new fields locally.
However, when I trigger the sync from the App, I get a conflict error in the service and the error occur when the changed table is hit.
"This error occurs when there is a conflict with the current state of the resource."

You mentioned - manually delete the resource and run azd up or azd provision again to re-create the resource from scratch.

Do I delete the whole resource group? Or do I delete the Azure App Service only? Do I delete the database too?

Thanks for any guidance!

[blmiles]

Never mind. All solved.

Once in Prod, I'll need to look at migrations in relation to EF Core in both client and service. But this worked for now and expedites continuous dev work for now.