Composite Tools: Fix plumbing for on-error-continue config #3118
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
Fix a bug where broken config plumbing lead to ignored continue-on-error behavior in composite tools.
Details
While preparing for a demo of continue-on-error behavior, I encountered a surprising bug where my config for a skippable step was not respected.
Instead, the composite tool aborted.
Root Cause
This was a surprising bug, because I know an integration test exists. Upon closer inspection, you'll see our integration tests bypass much of our configuration plumbing, previously described here. The composite tools system is even more elaborate, since it has another step:
CRD config -> yaml -> rawConfig -> config -> data structures used in executionThe linked integration tests configures
data structures used in execution, so it missed the brokenconfig -> data structures used in executionstep.I chose not to write a regression test for this quick fix. Instead, I will be opening an issue that describes the systemic issue and breakdown the work to repair it.