Refactor specs for YamlProcessor
What does this MR do?
Related to #30066 (closed)
This MR is a preparation refactoring in view of having the YamlProcessor returning a result object rather than raising errors.
The first attempt to refactor YamlProcessor was done in !35737 (closed) but the MR turned out to be too large.
Given that we are going to change the way that errors are handled we first should modify the specs to define the error handling strategy in one place so that it would ease the refactoring later. This MR accomplishes that.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team