We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As of ZOOKEEPER-1908 the CLI supports running setAcl recursively
setAcl
I would like the Kazoo client to be able to do the same, to avoid having to issue multiple calls for every child zNode.
Something like: Kazoo.client.set_acls(path=path, acls=acls, recursive=True)
Kazoo.client.set_acls(path=path, acls=acls, recursive=True)
It's not uncommon to have a unique SASL (or other scheme) credential + ACLs assigned to their own parent zNode. For example, the chroot for Kafka.
chroot
Right now, if I'm not mistaken, if we want to change ACLs for that parent zNode, we have to:
Kazoo.client.set_acl
This is cumbersome, and would be great if we could do it recursively from the get-go.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What would you like to be added
As of ZOOKEEPER-1908 the CLI supports running
setAcl
recursivelyI would like the Kazoo client to be able to do the same, to avoid having to issue multiple calls for every child zNode.
Something like:
Kazoo.client.set_acls(path=path, acls=acls, recursive=True)
Why is this needed
It's not uncommon to have a unique SASL (or other scheme) credential + ACLs assigned to their own parent zNode. For example, the
chroot
for Kafka.Right now, if I'm not mistaken, if we want to change ACLs for that parent zNode, we have to:
Kazoo.client.set_acl
for each oneThis is cumbersome, and would be great if we could do it recursively from the get-go.
The text was updated successfully, but these errors were encountered: