support community extensions #4922
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Add support for different extensions catalogs defined in the
K6_EXTENSIONS_CATALOG
environment variable:cloud
(default) andoss
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 usingcloud run
, the test will fail at execution time, as the cloud runners do not support these extensions.Checklist
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.
Related PR(s)/Issue(s)
Closes #4884