Split specs and content using separate YAML documents
What does this MR do and why?
Related to Define CI components syntax (#377327 - closed)
Related to Use YAML documents for CI templates' instead of... (#387038 - closed)
In this MR we change spec:inputs:
and content:
for a component to be 2 separate documents in the YAML. This way when we use with:
inputs with other YAML files we can add inputs:
in a header document while keeping the existing content as-is.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Grzegorz Bizon