[Pulp-dev] Migrations for pulpcore when?

[David Davis]

Your plan to commit migrations after the content work makes sense to me (as
long as there’s no major db changes planned). I opened an issue here to
track this here:

https://pulp.plan.io/issues/4067

David


On Fri, Oct 5, 2018 at 4:17 PM Brian Bouterse <bbouters at redhat.com> wrote:

> The plan has been for pulpcore to start shipping migrations when it
> reaches its RC. That is still a several weeks out, and that's challenging
> because some plugins, e.g. pulp_ansible, pulp_python, are fully-functional
> and have users using them. Those plugin would benefit from migrations, but
> they can't have them because they refer to migrations in pulpcore that
> don't exist the same on all systems. Django raises an exception (I tried
> with pulp_ansible).
>
> I'm wondering if we can commit migrations a bit earlier than that. The
> only major database change we have planned is the transition to
> single-content table (not MasterDetail). I'm wondering if:
>
> We can commit migrations to pulpcore after that is done?
> What other upcoming changes we know about for pulpcore 3.0 that have large
> database changes with them?
>
> Thanks!
> 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/20181005/e20a5d92/attachment.htm>