I can't speak to if these are all the correct level of access (thought it looks sane to me) but I am very excited about more granular permissions.
I would also say that I I think even an initial simpler implementation of this with just the "namespace admin" would go a long way to improving it if for some reason there is more complexity of realizing the whole plan of this PIP. This is something that we would likely have been tackling in the coming months, so happy to help wherever possible assuming that this PIP gets approved. On Wed, Nov 6, 2019 at 3:14 AM xiaolong ran <ranxiaolong...@gmail.com> wrote: > Hello all committers: > > About this PIP, do you have any other good ideas or propose. > > > -- > > Thanks > Xioalong Ran > > > > 在 2019年10月30日，下午7:49，xiaolong ran <ranxiaolong...@gmail.com> 写道： > > > > Hello all: > > > > When using pulsar-admin, I found that the current permission > verification mechanism has some problems. > > > > We are starting a proposal about permission levels and inheritance in > Apache Pulsar. > > > > The proposal is in: > > > https://github.com/apache/pulsar/wiki/PIP-49%3A-Permission-levels-and-inheritance > < > https://github.com/apache/pulsar/wiki/PIP-49:-Permission-levels-and-inheritance > > > > > > To ensure compatibility, these changes will be made in v4's admin api. > About the v4 admin API, see: > > > > https://github.com/apache/pulsar/wiki/PIP-48%3A-hierarchical-admin-api < > https://github.com/apache/pulsar/wiki/PIP-48:-hierarchical-admin-api> > > > > Looking forward to any feedback. > >
