myriation/headscale
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity
headscale/integration
History
Kristoffer Dalby ed4e19996b
Use tailscale key types instead of strings (#1609) 
* upgrade tailscale

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* make Node object use actualy tailscale key types

This commit changes the Node struct to have both a field for strings
to store the keys in the database and a dedicated Key for each type
of key.

The keys are populated and stored with Gorm hooks to ensure the data
is stored in the db.

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* use key types throughout the code

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* make sure machinekey is concistently used

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* use machine key in auth url

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* fix web register

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* use key type in notifier

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* fix relogin with webauth

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

---------

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2023-11-19 22:37:04 +01:00
..
dockertestutil give ci more tollerance for timeouts 2023-09-19 10:20:21 -05:00
hsic remove the use key stripping and store the proper keys (#1603) 2023-11-16 17:55:29 +01:00
integrationutil Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic give ci more tollerance for timeouts 2023-09-19 10:20:21 -05:00
acl_test.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
auth_oidc_test.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
auth_web_flow_test.go introduce a version subset we must test against 2023-09-05 08:47:43 +02:00
cli_test.go Use tailscale key types instead of strings (#1609) 2023-11-19 22:37:04 +01:00
control.go Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
embedded_derp_test.go add lock around saving ts clients 2023-09-19 10:20:21 -05:00
general_test.go Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
run.sh add script to run integration tests 2023-09-05 08:47:43 +02:00
scenario.go Upgrade Go 1.21, Tailscale 1.50 and add Capability version support (#1563) 2023-09-28 12:33:53 -07:00
scenario_test.go Handle errors in integration test setups 2023-09-05 08:47:43 +02:00
ssh_test.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
tailscale.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
utils.go give ci more tollerance for timeouts 2023-09-19 10:20:21 -05: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 locally

The easiest way to run tests locally is to use [act](INSERT LINK), a local GitHub Actions runner:

act pull_request -W .github/workflows/test-integration-v2-TestPingAllByIP.yaml

Alternatively, the docker run command in each GitHub workflow file can be used.

Running integration tests on GitHub Actions

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