Looks like we would like to move forward with adding a wrapper to the basic django-admin functionality as put forward in #5859 [0] to configure settings for users wanting to apply migrations. This was previously addressed with pulp-manager and removed in #4450 [1] due to lack of justification for middle-man and lack of autocompletion support.
I've tried to summarize the current decisions [2], but we really want consensus on: 1) the name (pulp-manage, pulp-manager, pulp-django-admin, pulpcore-admin) and 2) autocompletion status for this ticket (there's a linked doc but also a comment saying this functionality is undocumented) If folks could please take a look and reply on the issue so that the work may move forward, that would be much appreciated. [0] https://pulp.plan.io/5859 [1] https://pulp.plan.io/4450 [2] https://pulp.plan.io/issues/5859#note-26 Thank you in advance for your time. Dana Walker She / Her / Hers Software Engineer, Pulp Project Red Hat <https://www.redhat.com> dawal...@redhat.com <https://www.redhat.com>
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev