Add `k6 cloud project` and `k6 cloud project list` commands by oleiade · Pull Request #5650 · grafana/k6

oleiade · 2026-02-12T09:52:58Z

What?

This pull request introduces a new cloud project command group to the CLI, with a k6 cloud project list subcommand allowing users to list their Grafana Cloud k6 projects. It adds the implementation, command wiring, output formatting (including JSON support), and comprehensive tests for the new functionality.

Why?

As per #5644.

Checklist

I have performed a self-review of my code.
I have commented on my code, particularly in hard-to-understand areas.
I have added tests for my changes.
I have run linter and tests locally (make check) and all pass.

Checklist: Documentation (only for k6 maintainers and if relevant)

Please do not merge this PR until the following items are filled out.

I have added the correct milestone and labels to the PR.
I have updated the release notes: link
I have updated or added an issue to the k6-documentation: grafana/k6-docs#NUMBER if applicable
I have updated or added an issue to the TypeScript definitions: grafana/k6-DefinitelyTyped#NUMBER if applicable

Related PR(s)/Issue(s)

#5644

oleiade · 2026-02-12T09:54:29Z

Adding you as a reviewer @AgnesToulet as you've been working actively on this recently 🙇🏻

AgnesToulet · 2026-02-13T10:15:46Z

+		return c.outputJSON(resp.Value)
+	}
+
+	stackHeader := fmt.Sprintf("Projects for stack %d:\n\n", cloudConfig.StackID.Int64)


I think if we have the StackURL field non-empty, we should use it instead of the stack ID (but it might be empty).

AgnesToulet · 2026-02-13T10:17:23Z

+		return errors.New(
+			"no stack configured. Please run `k6 cloud login --stack <your-stack>` to set a default stack",
+		)


Might be worth creating a constant for this error, we'll probably use it a lot in other parts of the codebase in the future.

inancgumus

LGTM 🚀

joanlopez · 2026-03-24T11:27:25Z

Moving it to the next milestone to unlock the ongoing release process.

mstoykov · 2026-04-16T09:33:08Z

@oleiade it seems that this needs some updates 😬

joanlopez · 2026-04-16T10:18:24Z

+		t.Parallel()
+
+		srv := mockProjectListServer(t)
+		defer srv.Close()


I think this should be within a t.Cleanup(...), and perhaps, that could even be called inside mockProjectListServer, as it already receives t, and so this way no caller will ever forget to do so.

Wdyt?

joanlopez · 2026-04-16T10:21:09Z

+	listCmd.SetUsageTemplate(defaultUsageTemplate)
+	cloudProjectCommand.AddCommand(listCmd)
+
+	cloudProjectCommand.SetUsageTemplate(`Usage:


I see the list command help is convoluted, would make sense to use something like this there as well? I'm wondering if we should even define this as a function/const to be reused more widely.

joanlopez · 2026-04-16T10:24:46Z

+	if !checkIfMigrationCompleted(c.globalState) {
+		if err := migrateLegacyConfigFileIfAny(c.globalState); err != nil {
+			return err
+		}
+	}


Ideally, I'd prefer if we could do this in a single place. If not, it's okay.

I haven't digged into Cobra details since a while ago, so I forgot almost all my knowledge about it, but I was wondering if there's a way so any k6 cloud ... command executes this code, as a "pre-run" or something like that, but defined in a single place. Would that make sense? Not sure if possible, tho.

I guess the same reasoning could apply to the lines below, again, if possible, as ideally I'd like to not end up with the same code in ~20 places if we start adding support for more project operations or support for other types of resources (e.g., load tests).

joanlopez · 2026-04-16T10:27:31Z

+	if len(resp.Value) == 0 {
+		printToStdout(c.globalState, stackHeader+
+			"No projects found.\n"+
+			"To create a project, visit https://grafana.com/docs/grafana-cloud/testing/k6/projects/\n")


⚠️
The URL seems broken, I think it should be either of:

https://grafana.com/docs/grafana-cloud/testing/k6/projects-and-users/

https://grafana.com/docs/grafana-cloud/testing/k6/projects-and-users/projects/

joanlopez · 2026-04-16T12:48:30Z

+
+	if !cloudConfig.StackID.Valid || cloudConfig.StackID.Int64 == 0 {
+		return errors.New(
+			"no stack configured. Please run `k6 cloud login --stack <your-stack>` to set a default stack",


I think this suggestion is no longer consistent with #5833
cc/ @codebien

In other words; if I run this k6 cloud login --stack <your-stack>, it will throw an error, so it's better if we suggest something that will work from the first attempt.

Suggested change

"no stack configured. Please run `k6 cloud login --stack <your-stack>` to set a default stack",

"no stack configured. Please run `k6 cloud login` to set a default stack",

I agree. We should just suggest k6 cloud login. However, we already have this logic for checking the user session. We should reuse that logic from a shared place so we don't reinvent the wheel here.

oleiade added this to the v1.7.0 milestone Feb 12, 2026

oleiade self-assigned this Feb 12, 2026

oleiade requested a review from a team as a code owner February 12, 2026 09:52

oleiade requested review from inancgumus and mstoykov and removed request for a team February 12, 2026 09:52

oleiade added the feature label Feb 12, 2026

oleiade changed the title ~~feat: add k6 cloud project, and k6 cloud project list commands~~ Add k6 cloud project and k6 cloud project list commands Feb 12, 2026

oleiade requested a review from AgnesToulet February 12, 2026 09:54

oleiade mentioned this pull request Feb 12, 2026

Extend k6 cloud command abilities #5644

Open

oleiade temporarily deployed to azure-trusted-signing February 12, 2026 10:00 — with GitHub Actions Inactive

oleiade temporarily deployed to azure-trusted-signing February 12, 2026 10:02 — with GitHub Actions Inactive

oleiade force-pushed the feat/cloud-project-list branch from 8773e25 to 021ae2f Compare February 12, 2026 10:30

oleiade temporarily deployed to azure-trusted-signing February 12, 2026 10:37 — with GitHub Actions Inactive

oleiade temporarily deployed to azure-trusted-signing February 12, 2026 10:39 — with GitHub Actions Inactive

oleiade temporarily deployed to azure-trusted-signing February 12, 2026 14:58 — with GitHub Actions Inactive

oleiade temporarily deployed to azure-trusted-signing February 12, 2026 15:01 — with GitHub Actions Inactive

oleiade temporarily deployed to azure-trusted-signing February 13, 2026 08:01 — with GitHub Actions Inactive

oleiade temporarily deployed to azure-trusted-signing February 13, 2026 08:04 — with GitHub Actions Inactive

AgnesToulet reviewed Feb 13, 2026

View reviewed changes

inancgumus reviewed Feb 27, 2026

View reviewed changes

inancgumus approved these changes Feb 27, 2026

View reviewed changes

joanlopez modified the milestones: v1.7.0, v2.0.0 Mar 24, 2026

codebien mentioned this pull request Apr 15, 2026

Enforce stack info for cloud commands #5833

Open

feat: add k6 cloud project, and k6 cloud project list commands

54a482d

mstoykov force-pushed the feat/cloud-project-list branch from b1a3519 to 54a482d Compare April 16, 2026 09:30

joanlopez reviewed Apr 16, 2026

View reviewed changes

joanlopez mentioned this pull request Apr 16, 2026

cloud: migrate run and upload to v6 API #5769

Open

	"no stack configured. Please run `k6 cloud login --stack <your-stack>` to set a default stack",
	"no stack configured. Please run `k6 cloud login` to set a default stack",

Conversation

oleiade commented Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What?

Why?

Checklist

Checklist: Documentation (only for k6 maintainers and if relevant)

Related PR(s)/Issue(s)

Uh oh!

oleiade commented Feb 12, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

inancgumus left a comment

Choose a reason for hiding this comment

Uh oh!

joanlopez commented Mar 24, 2026

Uh oh!

mstoykov commented Apr 16, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

joanlopez Apr 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

oleiade commented Feb 12, 2026 •

edited

Loading

joanlopez Apr 16, 2026 •

edited

Loading