Prevent 500 errors when evaluating empty changelog configs
What does this MR do and why?
Prevent 500 errors when evaluating empty changelog configs
In 17.2 we fixed an issue when loading the changelog config yaml !156938 (merged)
This change caught errors from Psych when loading the YAML file. This didn't take into account empty YAML files.
These changes check the output from safe_load to ensure there was something loaded before trying to parse the config.
If nothing was loaded we return the default config.
Co-authored-by: @nav-j Changelog: fixed
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.