Skip to content

Move YamlProcessor::FeatureFlags to Ci::Config

Furkan Ayhan requested to merge 455627-ci-config-feature-flags into master

What does this MR do and why?

We implemented YamlProcessor::FeatureFlags to be used in places where we can't reach the context like project. We always used it in CI Entry classes. And they are only in the Ci::Config scope. So, it is safer to move this to Ci::Config.

The main reason we are doing this change now is that we recently had an incident because Ci::Config was called outside of the YamlProcessor scope and it tried to call YamlProcessor::FeatureFlags.

For the next step, we can change the class name from YamlProcessor::FeatureFlags to Ci::Config::FeatureFlags.

Related to #455627 (closed)

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.

Merge request reports