[Pulp-dev] [Breaking] Stopping the installer from auto-creating migrations - Sept 3rd

Austin Macdonald austin at redhat.com
Tue Aug 27 18:19:15 UTC 2019

This all sounds good to me. FYI, I closed https://pulp.plan.io/issues/5361
as a dupe since https://pulp.plan.io/issues/5321 has already been added to
the sprint. Feel free to use 5361 and close 5321 if you prefer.

On Tue, Aug 27, 2019 at 2:16 PM Brian Bouterse <bmbouter at redhat.com> wrote:

> tl;dr if we make this change on Sept 3rd, the installer won't auto-create
> migrations anymore. For every change needing a migration, please commit one.
> # Background
> We enabled the installer to "auto-create" migrations as a solution to the
> problem of them changing a crazy amount early on in Pulp3's development.
> Now the migrations are expected to be checked in and I believe they are for
> all plugins. This is only a breaking change for a plugin that is missing
> migrations.
> # The Problem
> https://pulp.plan.io/issues/5361 This was originally reported by Katello
> as a P2; I added details to it.
> # Feedback
> If there is something better that we should do please suggest it on the
> issue. If this is a concern or not going to work for you or our users
> please bring that up anywhere.
> # Timeline
> If there are no blocking concerns, I plan to make this change on Tuesday
> Sept 3rd.
> Thank you!
> Brian
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190827/5f11e372/attachment.htm>

More information about the Pulp-dev mailing list