Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

K6_CLOUD_TOKEN should be configurable per run #101

Open
zerok opened this issue Dec 12, 2023 · 0 comments
Open

K6_CLOUD_TOKEN should be configurable per run #101

zerok opened this issue Dec 12, 2023 · 0 comments

Comments

@zerok
Copy link
Contributor

zerok commented Dec 12, 2023

Right now it looks like K6_CLOUD_TOKEN can only be set globally for the whole process. This way, means that right now every canary that uses the same load balancer also has to upload data to the same k6 cloud instance:

flowchart LR
    canary1-->k6-loadtester
    canary2-->k6-loadtester
    canary3-->k6-loadtester
    k6-loadtester-->k6-cloud1
Loading

If we wanted to have different k6 cloud instances receive data from different canaries, we'd need to set up multiple k6-loadtester instances:

flowchart LR
    canary1-->k6-loadtester1
    canary2-->k6-loadtester2
    canary3-->k6-loadtester3
    k6-loadtester1-->k6-cloud1
    k6-loadtester2-->k6-cloud2
    k6-loadtester3-->k6-cloud3
Loading

It would be great if that token could also be injected by the webhook call itself so that multiple k6 cloud projects could be used for different canary tests while still using only a single webhook-handler instance.

flowchart LR
    canary1-->k6-loadtester
    canary2-->k6-loadtester
    canary3-->k6-loadtester
    k6-loadtester-->k6-cloud1
    k6-loadtester-->k6-cloud2
    k6-loadtester-->k6-cloud3
Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant