[test-operator] Improve variables overwriting #3446
+1
−4
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.
As part of processing test-operator stages, there is a task that takes all defined Ansible variables and overrides them with matching stage-specific variables. However, this task focuses in the end only on variables specific to test-operator. Yet, because the filtering is done on Ansible task-level, we end up with 80% of the
ansible-post-deployment.logfilled with entries likeskipping <variable_name>. To make this worse, it exposes some deployment-time secrets as a side-effect.This commit moves the filtering from task-level to earlier phase ~ when the loop arguments are prepared, so we will do override only on the test-operator-related variables, reducing the useless output and avoiding secrets exposure.