Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1384 +/- ##
=======================================
Coverage 95.03% 95.03%
=======================================
Files 43 43
Lines 2780 2780
=======================================
Hits 2642 2642
Misses 138 138 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| To run the stack: | ||
|
|
||
| 1. In the root directory run `git submodule update --init --recursive` to initialise the example-services repo | ||
| 2. Run `docker compose up -d` to launch an instance of NumTracker, RabbitMQ, Keycloak, Tiled, OPA and a number of IOCs, in detached mode |
There was a problem hiding this comment.
Does this work from the root of the repo? I think you either need to run from the system_tests directory or pass the file directly.
docker compose -f tests/system_tests/compose.yaml up -d
|
|
||
| 1. In the root directory run `git submodule update --init --recursive` to initialise the example-services repo | ||
| 2. Run `docker compose up -d` to launch an instance of NumTracker, RabbitMQ, Keycloak, Tiled, OPA and a number of IOCs, in detached mode | ||
| 3. Run `blueapi -c tests/system_tests/config.yaml serve` to launch BlueAPI configured to use the launched stack. This may take a while, as BlueAPI will attempt to connect to a number of devices via Channel Access |
There was a problem hiding this comment.
If you run source tests/system_tests/.env first, the devices will connect and it'll be a fair bit quicker.
|
|
||
| 1. Run `blueapi -c tests/system_tests/config.yaml login` | ||
| 2. Follow the login prompt to Keycloak, then log in with the username `admin` and password `admin` | ||
| 3. When promped by Keycloak, grant BlueAPI access to the listed privileges |
There was a problem hiding this comment.
| 3. When promped by Keycloak, grant BlueAPI access to the listed privileges | |
| 3. When prompted by Keycloak, grant BlueAPI access to the listed privileges |
|
|
||
| To log in through the BlueAPI CLI: | ||
|
|
||
| 1. Run `blueapi -c tests/system_tests/config.yaml login` |
There was a problem hiding this comment.
I don't think login requires the config file as the server is on the default host and port but worth adding a comment that it's needed if you want to run a plan with stomp config.
2 participants
Add tutorial on running local auth stack for debugging / developing auth stuff