Apply to v0.55 and v0.54

grafana · Dec 2, 2024 · 39c9928 · 39c9928
1 parent 2020dd6
commit 39c9928
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 10 deletions.
diff --git a/docs/sources/k6/v0.54.x/results-output/real-time/cloud.md b/docs/sources/k6/v0.54.x/results-output/real-time/cloud.md
@@ -113,7 +113,7 @@ command: `k6 cloud run --local-execution --no-archive-upload script.js`.
 
 ## Advanced settings
 
-A few [environment variables](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/environment-variables) can control how k6 streams results with `-o cloud`.
+A few [environment variables](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/environment-variables) can control how k6 streams results with `k6 cloud run script.js --local-execution`.
 
 When streaming, k6 will collect all data and send it to the cloud in batches.
 

diff --git a/docs/sources/k6/v0.54.x/testing-guides/running-large-tests.md b/docs/sources/k6/v0.54.x/testing-guides/running-large-tests.md
@@ -174,17 +174,16 @@ If you need the response body for some requests, override the option with [Param
 
 ### When streaming, use `--no-thresholds` and `--no-summary`
 
-If you're running a local test and streaming results to the cloud (`k6 run -o cloud`), you might want to disable the terminal summary
-and local threshold calculation, because the cloud service will display the summary and calculate the thresholds.
+If you're running a local test and streaming results to the cloud (`k6 cloud run script.js --local-execution`), you might want to disable the terminal summary and local threshold calculation, because the cloud service will display the summary and calculate the thresholds.
 
 Without these options, the operations will be duplicated by both the local machine and the cloud servers.
 This will save some memory and CPU cycles.
 
 Here are all the mentioned flags, all in one:
 
 ```bash
-k6 run scripts/website.js \
-  -o cloud \
+k6 cloud run scripts/website.js \
+  --local-execution \
   --vus=20000 \
   --duration=10m \
   --no-thresholds \

diff --git a/docs/sources/k6/v0.55.x/results-output/real-time/cloud.md b/docs/sources/k6/v0.55.x/results-output/real-time/cloud.md
@@ -113,7 +113,7 @@ command: `k6 cloud run --local-execution --no-archive-upload script.js`.
 
 ## Advanced settings
 
-A few [environment variables](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/environment-variables) can control how k6 streams results with `-o cloud`.
+A few [environment variables](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/environment-variables) can control how k6 streams results with `k6 cloud run script.js --local-execution`.
 
 When streaming, k6 will collect all data and send it to the cloud in batches.
 

diff --git a/docs/sources/k6/v0.55.x/testing-guides/running-large-tests.md b/docs/sources/k6/v0.55.x/testing-guides/running-large-tests.md
@@ -174,17 +174,16 @@ If you need the response body for some requests, override the option with [Param
 
 ### When streaming, use `--no-thresholds` and `--no-summary`
 
-If you're running a local test and streaming results to the cloud (`k6 run -o cloud`), you might want to disable the terminal summary
-and local threshold calculation, because the cloud service will display the summary and calculate the thresholds.
+If you're running a local test and streaming results to the cloud (`k6 cloud run script.js --local-execution`), you might want to disable the terminal summary and local threshold calculation, because the cloud service will display the summary and calculate the thresholds.
 
 Without these options, the operations will be duplicated by both the local machine and the cloud servers.
 This will save some memory and CPU cycles.
 
 Here are all the mentioned flags, all in one:
 
 ```bash
-k6 run scripts/website.js \
-  -o cloud \
+k6 cloud run scripts/website.js \
+  --local-execution \
   --vus=20000 \
   --duration=10m \
   --no-thresholds \