Should I rely on K6_CLOUD_TOKEN validation or explicit --out=cloud flag to prevent accidental public test exposure?
Preventing Accidental Public Access in k6 Cloud Tests When running k6 load tests that target the cloud service, there's a risk of unintentionally exposing test scripts and results publicly. The k6 cloud command makes tests visible by default unless explicitly configured otherwise. Two documented approaches exist for preventing this exposure: using the K6_CLO
k6