Repository navigation
k6 1.8.0 contains a breaking change related to the secret source #6093
Description
Brief summary
After the update from 1.7 to 1.8.0 the load tests fail due to the secret source change.
k6 version
1.8.0
OS
Linux
Docker version and image (if applicable)
No response
Steps to reproduce the problem
We run k6 using this command:
K6_CLOUD_PROJECT_ID=ID K6_CLOUD_TOKEN=token K6_SUMMARY_MODE=full k6 cloud run --secret-source=file=secrets.file --local-execution --no-archive-upload --include-system-env-vars index.ts
Expected behaviour
No errors after updating from 1.7 to 1.8.0
Actual behaviour
The runs fail with level=error msg="Uncaught (in promise) no secret source with name \"default\" is configured".
We wanted to highlight this.
Activity
joanlopez commentedon Jun 30, 2026
Hi @dominik-kropp,
Thanks for reporting it. The reason why it's failed is because since k6 v1.8.0, Cloud secrets are now automatically available in
k6 cloud run --local-execution. That's what's causing there to be more than one secret source (the Cloud enabled by default plus the file one your explicitly enabling), and therefore there's no "default".I'll bring it to our next team sync to decide what to do next; either stop enabling Cloud secrets by default in v1.x (and leave that only for v2.x) or perhaps setting the user-specified source as the default one, if possible and makes sense.
Apologies for this. In the meantime, you can either use
--no-cloud-secretsto opt out, if you're not interested in Cloud secrets, so this will leave the number of sources back to 1 and therefore a "default" one. Or by adjusting your script to specifically get the secret from your "file" source.I hope that helps! 🙇🏻
joanlopez commentedon Aug 12, 2026
Hi @dominik-kropp,
We've merged #6274, and it will be part of k6 v1.8.1, which is going to be released soon.
Again, thanks for reporting this 🫶