-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change database migration to be done with Entity Framework tooling in the release pipeline instead of with yuniql during application start #190
Labels
kind/chore
Non functional, often repeating tasks
Comments
6 tasks
Spinning the namespace-change out in a separate task (#212) as this requires some additional logistics/coordination with consumers. |
5 tasks
2 tasks
See also #264 |
Disconnecting this as a child of the KRR focused issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Find out how to set up EF tooling to perform database migration and add a release pipeline step. It's a goal to use the same mechanism to perform database migration for local developlent using Aspire.
Additional information
The altinn-studio team is already doing database migration this way.
https://github.com/Altinn/altinn-studio/blob/main/backend/Migrations.Dockerfile
Tasks
Acceptance criteria
The text was updated successfully, but these errors were encountered: