diff --git a/src/data/markdown/docs/03 cloud/01 Creating and running a test/02 Running a test from the CLI.md b/src/data/markdown/docs/03 cloud/01 Creating and running a test/02 Running a test from the CLI.md index 2197e13666..26b370efc9 100644 --- a/src/data/markdown/docs/03 cloud/01 Creating and running a test/02 Running a test from the CLI.md +++ b/src/data/markdown/docs/03 cloud/01 Creating and running a test/02 Running a test from the CLI.md @@ -113,6 +113,7 @@ export let options = { loadimpact: { name: 'Hello k6 cloud!', projectID: 123456, + staticIPs: true, distribution: { distributionLabel1: { loadZone: 'amazon:us:ashburn', percent: 50 }, distributionLabel2: { loadZone: 'amazon:ie:dublin', percent: 50 }, @@ -127,6 +128,7 @@ export let options = { | name (string) | Optional. The name of the main script file, so something like "script.js". | The name of the test in the k6 Cloud UI. Test runs with the same name will be grouped together. | | projectID (number) | Optional. It is empty by default. | The ID of the project in which the test is assigned in the k6 Cloud UI. By default, the default project of the user default organization. | | distribution (object) | Optional. The equivalent of `someDefaultLabel: { loadZone: "amazon:us:ashburn", percent: 100 }`. | How the traffic should be distributed. The keys are string labels that will be injected as [environment variables](/using-k6/environment-variables) on the appropriate nodes (matching the `loadZone`): `__ENV["someDefaultLabel"]` | +| staticIPs (boolean) | Optional. `false` by default | When set to `true` the cloud system will use dedicated IPs assigned to your organization to execute the test. | ### List of supported load zones