After some discussion on the issue[0], I decided not to commit the
migrations at this time. For me, the most relevant reason was that plugins
will be in various states of makemigration readiness, so we have to account
for that uncertainty at installation time whether we commit the migrations
of
Users who install using Ansible + pip/git cannot run the db-reset script.
(Ansible reset_db role will fail.) `pulp-manager` works for pip/git users
as well as developers because it already has an entrypoint in platform's
setup.py. Thanks Filip!
This relates to another issue, which is that
+1 to committing our migrations before the alpha. I like the idea of having
new migrations in the PR that involves model changes.
I don’t know what kind of conflicts should arise but the only time I think
we should consider recreating all the migrations is after we do a release
where we don’t
Today I filed and fixed https://pulp.plan.io/issues/3012, which is an issue
related to creating the migrations in the right order. It is a temporary
problem that we will have until we take the step of committing the
migrations to version control.
The reason migrations are not in git right now is
