Allow stages to be properly disabled by fixing the CLI parsing #786
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.
This fixes #775 - now
K6_STAGES="" k6 run script.js
can properly overwrite stages defined in the script andk6 run --stage ""
can overwrite stages configured by environment variables or from the script.The
len(conf.Stages) == 0
check covers both cases where stages arenil
(i.e. weren't defined at all) and where they have been explicitly disabled from an upper configuration tier (empty slice).I started to do some sort of robust end-to-end configuration testing framework for the future, but I postponed it for the future and just left a TODO since we'd have to refactor how we deal with the configuration a lot to be able to end-to-end test things properly... We also need to refactor it for a bunch of other reasons, so we'd do it then anyway.