Re: PIP 49: Permission levels and inheritance

On Wed, Oct 30, 2019 at 10:11 AM xiaolong ran wrote: > > Thanks Matteo and Joe. > > In here, I have two questions: > > 1. In `namespaces` and `topics`, most of the commands are `tenant admin`, are > they reasonable? I think having the intermediate step of namespace admin is good. For topics, we

Re: PIP 49: Permission levels and inheritance

Thanks Matteo and Joe. In here, I have two questions: 1. In `namespaces` and `topics`, most of the commands are `tenant admin`, are they reasonable? 2. Whether permissions management should be inherited? For examples: in `bin/pulsar-admin topics create [topic name]`, should only the `tenant

Re: PIP 49: Permission levels and inheritance

Agree with Joe, there are several methods in namespaces API that *really* meant for super-user only. It was not a mistake or oversight. >From `set-subscribe-rate` to `set-max-producers-per-topic`, all these methods are there for protecting the system and give the operator the flexibility to box u

Re: [PIP-48] Hierarchical admin api

Hi Florentin, I have bit of trouble understanding the motivation and scope of this proposal. There seems to be a mix of multiple different items. > Also, Pulsar evoled to the ability to manage multiple clusters. Pulsar had the ability of managing multiple clusters from day 0 (or I should say d

[PIP-48] Hierarchical admin api

Hello, We (Steven and I) have written a draft of pulsar improvement proposal about the admin api. We would like to get some feedback/review about it :D The pip is here: https://gist.github.com/FlorentinDUBOIS/4f98c0f71bf6514309b0414290b48e6a Feel free to contact me on slack or on this mai

Re: Apache Pulsar coding guide

Shall we add a coding guide for Apache Pulsar? Do you have any advice on it? For details, refer to https://github.com/apache/pulsar/pull/5494. Best Regards, Jennifer On Tue, Oct 29, 2019 at 11:10 PM Jinfeng Huang wrote: > Hi all, > When our users read the contributing guidelines at > https://p

Re: PIP 49: Permission levels and inheritance

It is good that we are looking at revamping the system. But the proposal as it is, is thin. First I would like this proposal to be split into two. One for inheritance and another for changes from existing controls. They are completely orthogonal and independent issues. Second, both of them (inher

[GitHub] [pulsar-client-node] gperinazzo edited a comment on issue #56: Add listener support for consumer

gperinazzo edited a comment on issue #56: Add listener support for consumer URL: https://github.com/apache/pulsar-client-node/pull/56#issuecomment-547925323 > The docker image used in CI was upgraded 5 days ago, and the nodejs version was also upgraded from v10.14.1 to v10.17.0. Didn

[GitHub] [pulsar-client-node] gperinazzo commented on issue #56: Add listener support for consumer

gperinazzo commented on issue #56: Add listener support for consumer URL: https://github.com/apache/pulsar-client-node/pull/56#issuecomment-547925323 > The docker image used in CI was upgraded 5 days ago, and the nodejs version was also upgraded from v10.14.1 to v10.17.0. Didn't see that

Invitation to Apache Pulsar Meetup | Shanghai on 11/16

Dear Pulsar community, We’re hosting Apache Pulsar Meetup | Shanghai on 11/16. The meetup provides an opportunity for Pulsar users, contributors, committers and PMC members to get together and share Pulsar updates. The upcoming meetup mainly covers: - Pulsar adoption stories at Orange Fin

PIP 49: Permission levels and inheritance

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-inhe

Jenkins build is back to normal : pulsar-website-build #795

See