Migration Issue about django-ca HOT 7 CLOSED

from django-ca.

Hi!
Thanks for reply!
django=3.2.10
django-ca=1.19.0
python 3.8.10

Update django_ca from 1.16.0 to 1.19.0

There are migrations which should be applied
But when I try to check or create new migrations, I received new migration 27 in library

from django-ca.

Hi,
I unfortunately still struggle to reproduce this issue. I do have a good theory by now, though. Maybe you can help me confirm it:

First, What's the value of your DEFAULT_AUTO_FIELD setting? I'm guessing it is django.db.models.AutoField - no "Big" in there, right?

If I'm right, an you please test two things?

First, in django_ca/app.py, set default_auto_field, like so:

--- a/ca/django_ca/apps.py
+++ b/ca/django_ca/apps.py
@@ -21,5 +21,6 @@ from django.utils.translation import gettext_lazy as _
 
 
 class DjangoCAConfig(AppConfig):  # pylint: disable=missing-class-docstring
+    default_auto_field = "django.db.models.BigAutoField"
     name = "django_ca"
     verbose_name = _("Certificate Authority")

This should make the issue go away cleanly - if my theory is right.

Second, in your settings, try setting DEFAULT_AUTO_FIELD = "django.db.models.BigAutoField". This should make the django-ca migration go away as well (but will introduce the same migrations in other apps, if you have any).

Can you confirm both? If yes, I will apply the patch to app.py, which should be a permanent fix for this scenario. The fix will be in the soon-to-be-released 1.20.0 (so you could leave your patch in place as a workaround, if that is feaseable to you).

from django-ca.

Hi!)
Yes, is it.
Currently DEFAULT_AUTO_FIELD=django.db.models.AutoField in settings.py

I will test it today!
Thank you!

from django-ca.

Hi!
According your suggest I checked 1st test and

Its work :)

Thank you!

from django-ca.

Hi,

I will be releasing django-ca 1.19.1 which will fix the issue (and add explicit support for Django 4.0 and cryptography 36). I will close this issue once it's released (currently still running the tox test suite).

Thank you for using django-ca. Please let me know if you have any further issues!

kr, Mat

from django-ca.

I just published 1.19.1, it includes the fix from the commit above. Please let me know if you have any further issues.

kr, Mat

from django-ca.