Skip to content

support community extensions #4922

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: binary-provisioning/enable-to-all-users
Choose a base branch
from

Conversation

pablochacin
Copy link
Contributor

@pablochacin pablochacin commented Jul 11, 2025

What?

Add support for different extensions catalogs defined in the K6_EXTENSIONS_CATALOG environment variable: cloud (default) and oss for community extensions. This catalog is sent as part of the requests to the build service.

Why?

By default, binary provisioning only supports extensions defined in the cloud catalog.

We want to offer users the possibility of opting in for the complete catalog of extensions when running tests locally.

Note: if the user specifies the oss catalog and sends a test to the cloud using cloud run, the test will fail at execution time, as the cloud runners do not support these extensions.

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)

Closes #4884

@pablochacin pablochacin force-pushed the binary-provisioning/support-community-extensions branch 3 times, most recently from 5456052 to 6eb7e09 Compare July 17, 2025 19:06
@pablochacin pablochacin force-pushed the binary-provisioning/support-community-extensions branch from 6eb7e09 to 18cb212 Compare July 22, 2025 13:14
@pablochacin pablochacin marked this pull request as ready for review July 22, 2025 16:17
@pablochacin pablochacin requested a review from a team as a code owner July 22, 2025 16:17
@pablochacin pablochacin requested review from ankur22 and AgnesToulet and removed request for a team July 22, 2025 16:17
@codebien codebien self-requested a review July 25, 2025 08:34
@pablochacin pablochacin added this to the v1.2.0 milestone Jul 25, 2025
@pablochacin pablochacin force-pushed the binary-provisioning/enable-to-all-users branch from 00af9c1 to 337ddaf Compare July 25, 2025 15:33
Signed-off-by: Pablo Chacin <pablochacin@gmail.com>
Signed-off-by: Pablo Chacin <pablochacin@gmail.com>
@pablochacin pablochacin force-pushed the binary-provisioning/support-community-extensions branch from 5a17ece to 8afaff8 Compare July 25, 2025 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants