myriation/headscale
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity
headscale/integration
History
Motiejus Jakštys bafb6791d3 oidc: allow reading the client secret from a file 
Currently the most "secret" way to specify the oidc client secret is via
an environment variable `OIDC_CLIENT_SECRET`, which is problematic[1].
Lets allow reading oidc client secret from a file. For extra convenience
the path to the secret will resolve the environment variables.

[1]: https://systemd.io/CREDENTIALS/
2023-01-14 17:03:57 +01:00
..
dockertestutil oidc: add test for expiring nodes after token expiration 2023-01-04 09:23:52 +01:00
hsic oidc: allow reading the client secret from a file 2023-01-14 17:03:57 +01:00
integrationutil Remove some very verbose error outputs 2022-11-21 14:37:50 +01:00
tsic Add logout method to tsic 2022-12-22 00:09:21 +01:00
auth_oidc_test.go oidc: allow reading the client secret from a file 2023-01-14 17:03:57 +01:00
auth_web_flow_test.go Make WaitForTailscaleLogout a Scenario method 2022-12-22 20:02:18 +01:00
cli_test.go Port integration tests routes CLI to v2 2022-12-06 08:17:14 +01:00
control.go Added integration tests for ephemeral nodes 2023-01-05 14:59:02 +01:00
general_test.go Added integration tests for ephemeral nodes 2023-01-05 14:59:02 +01:00
README.md Add integration readme 2023-01-06 12:32:24 +01:00
scenario.go Added integration tests for ephemeral nodes 2023-01-05 14:59:02 +01:00
scenario_test.go Added integration tests for ephemeral nodes 2023-01-05 14:59:02 +01:00
ssh_test.go Mark the flag properly experimental 2022-11-26 11:53:31 +01:00
tailscale.go Add logout method to tsic 2022-12-22 00:09:21 +01:00

README.md

Integration testing

Headscale relies on integration testing to ensure we remain compatible with Tailscale.

This is typically performed by starting a Headscale server and running a test "scenario" with an array of Tailscale clients and versions.

Headscale's test framework and the current set of scenarios are defined in this directory.

Tests are located in files ending with _test.go and the framework are located in the rest.

Running integration tests on GitHub Actions

Each test currently runs as a separate workflows in GitHub actions, to add new test, add the new test to the list in ../cmd/gh-action-integration-generator/main.go and run go generate inside ../cmd/gh-action-integration-generator/ and commit the result.