What are the URL Endpoints of the Regional Controller?
| URL | Purpose |
|---|---|
| https://<RC_IP_address>/api/v1/ | This is the base URL for all of the API calls to the Regional Controller. |
| https://<RC_IP_address>/docs/ | This is the address of an online copy of the documentation for the Regional Controller. Note that because this documentation is built along with the codebase, it is likely to be more up to date than this wiki. |
| http://<RC_IP_address>:8080/admin/ | This is the console for the embedded copy of Apache® Airflow that is used as the workflow engine within the Regional Controller. |
...
As it is still being modified and in a state of flux, the full API is documented only in the online copy under https://<RC_IP_address>/docs/api.html
Alternately, you can clone the gerrit repository for the Regional Controller, and look at the markup files under /src/site/docs/.
...
| Username | Password | Roles | Purpose |
|---|---|---|---|
| admin | admin123 | create/read/update/delete all | This is the "super user" for RC; e.g. it has all roles and capabilities. |
| readonly | admin123 | read all | This user has read only access; e.g. it can issue GET requests, but cannot change objects or make new objects. |
| workflow | admin123 | read all, create podevents | This user is used internally in order to create POD events from within the workflows. |
| noaccess | admin123 | (none) | This user has no access at all. |
...