-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
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
[Feature Request] Azure Data Lake Gen 2 | Cascade security settings #1380
Comments
Hey @danielstocker, what CLI tools support this scenario? |
Sorry @MRayermannMSFT I wasn't clear at all in that statement. https://docs.microsoft.com/en-gb/rest/api/storageservices/datalakestoragegen2/path/list I realise that I made it sound like I'm thinking of a single CLI command to apply recursive permissions. |
Hi Daniel, Regarding support in ASE, I will let MRayermann respond. Thanks, |
For us, this is the type of feature we will wait for the APIs to support. |
Hi y'all, the storage service added an API that will allow us to do this. Thought I'm not sure if it'll be in a way that'll make y'all happy. We'll be adding a feature which uses this API in version 1.17. You can track that work here: #3695 I'm going to leave this issue open for a while in-case y'all have anything to say. Eventually I will close it in favor of issue #3695 though. Thanks. |
Hi all, 1.17 recently shipped with a feature that allows you to propagate the ACLs of a directory to all of it's existing descendants. Please give the feature a try and let us know if you have any feedback. Thanks! We'll monitor this issue for a bit and close it in the near future. 😊 |
Closing. If anyone has feedback feel free to open an issue. :) |
To my knowledge, there is currently no UI feature to reset and cascade security setting to child files and folders on the Azure Storage Explorer when using Azure Data Lake Gen2.
This is supported via the command line tools, but it would be nice to be able to reset and cascade permissions in Azure Storage Explorer directly.
The text was updated successfully, but these errors were encountered: