@ -16,11 +16,13 @@ only have a single update event every few minutes, we can authenticate only as n
Currently the only exposed actions that require authentication are Editor-based ones, so we aren't assigning roles or having granular permissions.
Currently the only exposed actions that require authentication are Editor-based ones, so we aren't assigning roles or having granular permissions.
Actions available via Thrimshim are:
Actions available via Thrimshim are:
* `get_row`: Return a single row from the database by ID. Unauthenticated.
* Unauthenticated Actions
* `get_all_rows`: Return the entire events table (or specific subsets of it), for building dashboards. Unauthenticated
* `get_row`: Return a single row from the database by ID. Unauthenticated.
* `update_row`: Updates row in the Events table. Authenticated and limited to Editors and Admins (who can update different sets of rows). Authenticated.
* `get_all_rows`: Return the entire events table (or specific subsets of it), for building dashboards. Unauthenticated
* `manual_link`: Override the `video_link` field in the Events Table, in case of a manual upload. Authenticated.
* Authenticated Actions
* `reset_row`: Clear `state` and `video_link` columns and reset `state` to 'UNEDITED' in Events table. Authenticated.
* `update_row`: Updates row in the Events table.
* `manual_link`: Override the `video_link` field in the Events Table, in case of a manual upload.
* `reset_row`: Clear `state` and `video_link` columns and reset `state` to 'UNEDITED' in Events table.
### Admin Access
### Admin Access
Node admins will connect directly to the database via third party tools (such as pgAdmin) for tasks such as adding members or manually overwriting the Events table.
Node admins will connect directly to the database via third party tools (such as pgAdmin) for tasks such as adding members or manually overwriting the Events table.
@ -30,5 +32,6 @@ Node admins will connect directly to the database via third party tools (such as