Stop having the installer call makemigrations (scheduled to merge Sept 3rd)
In pulp_rpm, some PRs have failed to include migration changes. This problem has been masked by the fact that the installer calls makemigrations.
I think most (or all?) plugins have migrations in source control. If a plugin chooses not to check their migrations in, they can create a custom ansible prereq role to call makemigrations.
*Note: This is a breaking change and was announced on pulp-dev here This was communicated to be announced Sept 3rd.
Updated by email@example.com over 4 years ago
+1, the time has come that this causes more trouble than it helps.
For whoever picks up this story, it would be very nice to put some thought and docs into how the migrations would be made for a new plugin. Specifically, I think it would be pretty unfriendly if a new plugin author needed to write an ansible role as a first step.
Updated by daviddavis about 4 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset ansible-pulp3|e94c435624e605e9a01018a61e97c6f02afd49f8.