s3 bucket names being stored directly in migrations about django-s3-storage HOT 5 CLOSED

I most often edit the migration files, import the module where I defined the storage and replace the storage=django_s3_storage... part with storage=app.storages.s3_storage or something.

It's not really recommended to import files from the project in migrations since you cannot move around anything without updating historical migrations as well. Since I add a module only for storages and I do not update it if possible at all after introducing it initially I'm fine.

(Customizing the deconstruction of the storage would be possible as well, but I sort-of like the workaround above even better.)

from django-s3-storage.

That's quite a problem!

The reason this comes about is that it's possible to have loads of different storage backends, all used in different model fields, and all will have their setting included in the migration. This is by design, and hard to change, even if it was desired. Presumably we'd need to differentiate between arguments passed via settings and via explicit settings.

The workaround from @matthiask is fine.

from django-s3-storage.

Thanks for the workaround, I will give it a try. I'm glad I noticed it before applying migrations to production. Out of curiosity, had I done that, where would the now-incorrect settings be visible? And would it be sending things to the wrong bucket or taking the settings set at runtime?

from django-s3-storage.

from django-s3-storage.

Ah, I see, thank you. I appreciate the help.

from django-s3-storage.