Skip to content
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

Remove ACL for a folder by one Rest API call #183

Open
jdzivy38 opened this issue Apr 26, 2024 · 1 comment
Open

Remove ACL for a folder by one Rest API call #183

jdzivy38 opened this issue Apr 26, 2024 · 1 comment
Labels
enhancement New feature or request REST Issue lies on deeper level of MSTR architecture (REST or iServer) and not on mstrio-py itself

Comments

@jdzivy38
Copy link

USE CASE:
I am planning to update ACLs for folders in a project:

  • Remove ACL
  • Add ACL
    I have found the method modify_rights to manage ACL for an object Folder: mstrio-py/mstrio/utils/acl.py at master · MicroStrategy/mstrio-py (github.com)

This method iterates through a list of folder’s ids and trustees and update the object Folder.
If I have 10 folder’s ids and 5 trustees in the list, finally 50 updates will be provided to complete it.

EXPECTATION:
Do I have any chance to remove ACL for a folder by an one Rest API call?
I haven’t found endpoint to remove a full ACL for a folder.

@apiotrowskiMicroStrategy apiotrowskiMicroStrategy added enhancement New feature or request REST Issue lies on deeper level of MSTR architecture (REST or iServer) and not on mstrio-py itself labels Oct 18, 2024
@apiotrowskiMicroStrategy
Copy link
Contributor

Hi @jdzivy38

This is something that would need to be implemented on REST API side, which mstrio can only consume when it exists.

Considering that, please raise the issue with our MSTR TechSupport to create a case (which then will be able to be prioritised and capacity for it found) and share here the CS ID for ease of reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request REST Issue lies on deeper level of MSTR architecture (REST or iServer) and not on mstrio-py itself
Projects
None yet
Development

No branches or pull requests

2 participants