#30490: migrations unique_index on (app, name).
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: Bug | Status: closed
Component: Uncategorized | Version: master
Severity: Normal | Resolution: wontfix
Keywords: migrations parallel | Triage Stage:
run | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tom Forbes):
The way we solved this with Kubernetes is to create and launch a Job which
will run manage.py migrate as part of the deployment pipeline. Once that
Job is complete, update the Deployment/ReplicaSet as needed.
As always you have to be completely sure the migration can run
concurrently with your app, but in genera running migrations as an initpod
or as part of the web app pod is really not advised, and adding a hack
like a distributed lock will only bring you pain.
--
Ticket URL: <https://code.djangoproject.com/ticket/30490#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.63ee7e4d8d49f87057b80d37d28ac5c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
