Improve storage validation after configuration structure update
What does this MR do?
Besides improving the error message to specify what exactly you need to do to solve the error, we now don't skip all storage validations on the test environment, so that you also get a nice error message if you're running tests. Now if conditions are met to skip valitaions (test env or env variable) we still make sure the settings look sane, we just skip verifying the paths exists and meet the given conditions.
Are there points in the code the reviewer needs to double check?
Does this need a changelog entry?
Why was this MR needed?
People were stumbling with errors since the configuration update got merged
Screenshots (if relevant)
This is how it looks now when running a test (before, you got a cryptic nil error.
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together