ConfigTracker: Scan envFrom in init-containers #914
Merged
+247
−1
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.
Currently, the ConfigTracker is not supported scanning initContainer's environments.
this PR supports that. it is useful when we want to switch the path to the data at the timing of starting initContainer.
How can I add tests to scan envFrom in initContainer?
I guess I would add the initContainer spec to the struct returned by the
newDeploymentControllerTest
method indeployment_fixture_test.go
.