Errors are obfuscated when using `include`
Description
When someone combines CI/CD configuration using include
keyword, in case of resulting configuration being invalid, when there is an error in the included file, error message is very vague an unclear. There are also errors when 'included yml is invalid' or 'not found/404'. There's also errors I've seen people report when including across SSL boundaries, or between projects with different access levels (403 type errors), that might be handy to have specific messages for.
These errors seem to be occurring more and more so improving the error reporting will help get to the bottom of the one or more issues resulting in that behavior. The current way this is working with the actual error hidden by the yaml error is considered a ~bug.
Errors to improve reporting on
- If included yml is invalid
- Not found/404
- Security/access errors (403-type)
- Transient errors (503, 502, etc.) - see linked issues for examples of intermittent issues