Skip to content

CLI Cloud commands: make stack info mandatory #5651

@AgnesToulet

Description

@AgnesToulet

Feature Description

The new stack option added to the Cloud configuration in #5420 should become as mandatory as the token information. If it's not provided, the command should fail.

It can be specified in different ways:

  • When running the k6 cloud login command with the --stack parameter or using the interactive mode (in this case, this should be the stack slug or full URL)
  • In the script options, adding the stackID option
  • In the env variables, using the K6_CLOUD_STACK_ID env variable

It would be nice to make the different options a bit more consistent and either use the stack slug everywhere, or support stack slug/url/id everywhere.

Suggested Solution (optional)

No response

Already existing or connected issues / PRs (optional)

No response

Metadata

Metadata

Labels

breaking changefor PRs that need to be mentioned in the breaking changes section of the release notescloudfeature

Type

No fields configured for Task.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions