Currently, when there are multiple allow/deny clauses, all of them produce "the same" output:
02:49:14.514 [INFO] Applied allow permissions for authorizable 'XYZ' at path '/content/your_project/abc'
...
02:49:14.734 [INFO] Applied deny permissions for authorizable 'XYZ' at path '/content/your_project/ab/cd'
The allow sets a handful of usually allowed operations on a given tree, while deny here uses glob = "STRICT" to prevent removing the given node (since the whole tree depends on it). Logs don't reveal that right away.
The glob = "STRICT" is a good fit to add to such a log, as being applied on a specific node can explain itself at a first glance.
Currently, when there are multiple
allow/denyclauses, all of them produce "the same" output:The
allowsets a handful of usually allowed operations on a given tree, whiledenyhere usesglob = "STRICT"to prevent removing the given node (since the whole tree depends on it). Logs don't reveal that right away.The
glob = "STRICT"is a good fit to add to such a log, as being applied on a specific node can explain itself at a first glance.