Thank you for sharing this use case outline with me. I am hoping we can prioritize rbac work like this. It's very important.
On Wed, Jun 2, 2021 at 11:35 AM Neal Gompa <ngomp...@gmail.com> wrote: > Hey Brian, > > Yes, for sure! I'm basically looking into using RBAC to support a > workflow like so: > > * Automation via a service account imports RPMs and DEBs into a pool > * Automation via another service account selects those packages to > publish into various staging repos > * Select users/groups can promote those packages to their assigned > "stable" repos > > The idea is that I can partition ACLs for various functions of Pulp to > prevent unwanted actions. > > > On Wed, Jun 2, 2021 at 10:56 AM Brian Bouterse <bmbou...@redhat.com> > wrote: > > > > Hi Neal, > > > > Apologies for the late reply. We've added the RBAC to various endpoints > in pulpcore and some plugins, but what I think would be helpful is if we > had a way to more clearly identify what has RBAC and what doesn't across > pulpcore and plugins. Would that be helpful? > > > > Thank you, > > Brian > > > > > > On Tue, May 25, 2021 at 11:46 AM Neal Gompa <ngomp...@gmail.com> wrote: > >> > >> On Tue, May 25, 2021 at 11:23 AM Brian Bouterse <bmbou...@redhat.com> > wrote: > >> > > >> > * Making top-level Authentication page in docs > >> > * https://pulp.plan.io/issues/8799 > >> > >> The docs currently mention that RBAC stuff is planned, is there > >> something that shows the status of that? This is something that I'd > >> love to see in Pulp sooner rather than later... > >> > >> > >> -- > >> 真実はいつも一つ！/ Always, there's only one truth! > >> > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-dev
