It certainly is! A few steps are needed:
- Figure out workspace ID (
rcc cloud workspace
) - Get token (
rcc cloud authorize -w <workspace ID>
) - Configure env variables in env.json:
"RC_WORKSPACE_ID": "<workspace ID",
"RC_API_SECRET_HOST": "
https://api.eu1.robocloud.eu
",
"RC_API_SECRET_TOKEN":"<Token>"
The token is quite short lived though, but this can certainly be used to make local runs closer to Cloud orchestrated runs.