Added feature to interpolate env vars in command args #637
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
This PR adds support for environment variable interpolation in the
argumentsfield of theTestRunCRD.Why
When running a k6 test with multiple pods, all pods try to generate the same output files (e.g.,
report.json). This leads to file overwrites and a loss of individual pod metrics. This change allows users to use environment variables like${POD_NAME}to create unique filenames for each pod's output, preventing data loss. For example,-o json=myoutput-${POD_NAME}.jsonwould now correctly generatemyoutput-k6-test-run-1.json,myoutput-k6-test-run-2.json, etc.Refers: #162
How
The
jobs/runner.gofile was updated to:TestRunCRD.argumentsstring and replace any$VARor${VAR}placeholders with their corresponding values.