You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if you could setup a Service in the azure.yaml to be able to run database schema scripts. This would enable azd deploy DBSchema for example to be run to deploy database changes only. Also, you could setup an 'App' service to be dependent on the 'DBSchema' service to be deployed first when running an azd up.
Currently, however, the only way to deploy database schema is to use on of the postprovision or postdeploy hooks to run the scripts to deploy the database schema after the provision step ran the Azure Bicep to provision the database.
AZD is a great tool, but it's lack of supporting database deployments, or even just the ability to setup a 'script' service to create custom Deployments, makes this tool a bit cumbersome when it comes to database deployments.
The text was updated successfully, but these errors were encountered:
@crpietschmann Currently Azd does not support azd deploy DBSchema to run database schema scripts, but you can use the resource Microsoft.Resources/deploymentScripts@2020-10-01 to run custom database schema scripts. This resource can execute any scripts you need during the provision process.
It would be nice if you could setup a Service in the
azure.yaml
to be able to run database schema scripts. This would enableazd deploy DBSchema
for example to be run to deploy database changes only. Also, you could setup an 'App' service to be dependent on the 'DBSchema' service to be deployed first when running anazd up
.Currently, however, the only way to deploy database schema is to use on of the
postprovision
orpostdeploy
hooks to run the scripts to deploy the database schema after theprovision
step ran the Azure Bicep to provision the database.AZD is a great tool, but it's lack of supporting database deployments, or even just the ability to setup a 'script' service to create custom Deployments, makes this tool a bit cumbersome when it comes to database deployments.
The text was updated successfully, but these errors were encountered: