feat: add TESTING environment variable feature gate for microvm-init #2264
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.
Summary
Add support for
TESTINGenvironment variable that gets passed to the kernel command line asmelange.testing=<value>. This allows us to feature within staging to test things. In particular, we'd like to make some changes to microvm-init.Changes
pkg/container/qemu_runner.goto readTESTINGenvironment variableTESTINGis a number (or empty string) to prevent injection issuesmelange.testing=<value>Usage
Security
The implementation validates that
TESTINGonly accepts numeric values (or empty string) to prevent kernel command line injection attacks. String values are rejected with a warning message.Test plan
TESTING=1and verifymelange.testing=1appears in kernel cmdlineTESTING=fooand verify warning is logged and value is not passedTESTING=and verifymelange.testing=is passed to kernelTESTINGenv var and verify no changes to existing behavior