The public Debug.DebugClear RPC deletes all persistent application state. While it is useful for development, there is no method-level authorization or server side role restricting it to a dedicated administrator.
Although authorization could be designed for this operation, exposing a remotely callable global wipe is unnecessary for the production API. It also requires the normal ateapi database role to have TRUNCATE privileges, which conflicts with the least-privilege runtime role design in #997
The public
Debug.DebugClearRPC deletes all persistent application state. While it is useful for development, there is no method-level authorization or server side role restricting it to a dedicated administrator.Although authorization could be designed for this operation, exposing a remotely callable global wipe is unnecessary for the production API. It also requires the normal
ateapidatabase role to haveTRUNCATEprivileges, which conflicts with the least-privilege runtime role design in #997