[Pulp-dev] django-admin wrapper for Pulp3
ipanova at redhat.com
Thu Feb 13 14:21:00 UTC 2020
Bump on this thread, please take a look and provide feedback on the issue!
Senior Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Mon, Jan 27, 2020 at 10:23 PM Dana Walker <dawalker at redhat.com> wrote:
> Looks like we would like to move forward with adding a wrapper to the
> basic django-admin functionality as put forward in #5859  to configure
> settings for users wanting to apply migrations. This was previously
> addressed with pulp-manager and removed in #4450  due to lack of
> justification for middle-man and lack of autocompletion support.
> I've tried to summarize the current decisions , but we really want
> consensus on:
> 1) the name (pulp-manage, pulp-manager, pulp-django-admin, pulpcore-admin)
> 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.
>  https://pulp.plan.io/5859
>  https://pulp.plan.io/4450
>  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>
> dawalker at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev