misc: run acceptance tests from github actions. #497
Conversation
Update tests and docs such that the entire acceptance test suite runs against the simulated omicron environment. We either document and script all resources that the tests depend on, or teach the tests to create the dependencies themselves. We'll look into running the acceptance suite against simulated omicron in a separate patch.
jmcarp
force-pushed
the
jmcarp/omicron-test-actions
branch
17 times, most recently
from
0d2439d to
cc443f5
Compare
jmcarp
changed the title
jmcarp
changed the title
| SHELL ["/bin/bash", "-c"] | ||
|
|
||
| RUN \ | ||
| git clone https://github.com/oxidecomputer/omicron.git --depth 1 --branch jmcarp/prereqs-omit-sudo && \ |
There was a problem hiding this comment.
Note: I had to make some small changes to the install scripts in omicron to get this to build. If we like this approach, I'll send a PR to omicron and stop pointing to my branch.
jmcarp
force-pushed
the
jmcarp/omicron-test-actions
branch
from
cc443f5 to
1b452f9
Compare
| @@ -0,0 +1,53 @@ | |||
| # /// script | |||
There was a problem hiding this comment.
This is a bit of a hack. To run these tests manually, the user would first run oxide auth login, but that's an interactive flow that requires a browser. To make this non-interactive, we add a script that simulates the device auth flow and prints a token. @david-crespo pointed out that we could instead support password login via the cli, with a warning not to use it in production, but IMO this is fine for the time being.
| }, | ||
| ) | ||
| token_resp.raise_for_status() | ||
| return token_resp.json()["access_token"] |
| go-version-file: 'go.mod' | ||
| - uses: docker/setup-compose-action@v1 | ||
| - uses: astral-sh/setup-uv@v6 | ||
| - name: install oxide cli |
There was a problem hiding this comment.
Just noting that we should probably consider creating a setup-oxide GitHub Action at some point.
| uv run auth.py | ||
| echo "OXIDE_TOKEN=$(uv run auth.py)" >> $GITHUB_OUTPUT |
There was a problem hiding this comment.
What's the purpose of running uv run auth.py twice? Should we just capture the result as a variable and echo it instead?
| SHELL ["/bin/bash", "-c"] | ||
|
|
||
| RUN \ | ||
| git clone https://github.com/oxidecomputer/omicron.git --depth 1 --branch jmcarp/prereqs-omit-sudo && \ |
Builds on #494.