An issue happens when deploying arches for science over an existing deployment - "duplicate key violates unique contstraint". This happens in the initial 0001 afs migration. This is strange because we call Plugin.objects.update_or_create - which should update the existing plugins rather than trying to pave them over. A cursory google suggests that the issue is likely that our filters for update_or_create are too restrictive. See the following
An issue happens when deploying arches for science over an existing deployment - "duplicate key violates unique contstraint". This happens in the initial 0001 afs migration. This is strange because we call Plugin.objects.update_or_create - which should update the existing plugins rather than trying to pave them over. A cursory google suggests that the issue is likely that our filters for update_or_create are too restrictive. See the following
https://stackoverflow.com/questions/50915911/django-update-or-create-gets-duplicate-key-value-violates-unique-constraint