Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
None
-
None
Description
For troubleshooting borked instances we should have a way to inspect (and write to?) the complete tree, including items that are hidden. Permission tree, version tree, indexes, etc come to mind.
We need to design this tool in a way that does not compromise security, but on the other hand I think we need write capabilities in order to fix broken items if needed. Not sure, how to best do this...
The tool ideally can be limited to look at
- specific paths only and
- ranges of MVCC revisions