I have tried to upgrade the version of the docker container that I created out of your application as you are aware of at here.
I encountered a problem while trying to run the migrations manually with manage.py db migrate and manage.py db stamp as you have described.
As it turns out while running the online migrations while trying to configure alembic.context, compare_types is defined twice as an argument, one explicitly and one I think from current_app.extensions['migrate'].configure_args and it was causing a panic .
Therefore, I would submit this PR for your review if it has no destructive changes, this change fixes the flow of the container, elsewise I can adapt it accordingly.
Hello again @Salamek,
I have tried to upgrade the version of the docker container that I created out of your application as you are aware of at here.
I encountered a problem while trying to run the migrations manually with
manage.py db migrate
andmanage.py db stamp
as you have described.As it turns out while running the online migrations while trying to configure
alembic.context
,compare_types
is defined twice as an argument, one explicitly and one I think fromcurrent_app.extensions['migrate'].configure_args
and it was causing a panic .Therefore, I would submit this PR for your review if it has no destructive changes, this change fixes the flow of the container, elsewise I can adapt it accordingly.