If a templated configuration fails for any reason, the TemplateConfiguration reason should reflect this
Current Behavior
Currently TemplateConfiguration and TemplateStep just grab the file's root result. This often does not contain any useful information. The current implementation assumes that a single checkout can be inspected in the report for failure reasons, but did not account for any nested checkouts.
Possible Solution
Walk down the templated file and aggregate failed results? (This seems annoying)
Write some text in the top-level result? (I want this at a minimum)
Expected Behavior
If a templated configuration fails for any reason, the TemplateConfiguration reason should reflect this
Current Behavior
Currently
TemplateConfigurationandTemplateStepjust grab the file's root result. This often does not contain any useful information. The current implementation assumes that a single checkout can be inspected in the report for failure reasons, but did not account for any nested checkouts.Possible Solution
Walk down the templated file and aggregate failed results? (This seems annoying) Write some text in the top-level result? (I want this at a minimum)
Context
241
Your Environment
pcds-5.8.4