Allow CI YamlProcessor to use feature flags with actor
Problem
Enabling new CI YAML keywords via feature flags incrementally is not possible today due to the Ci::Config
not propagating the project
actor throughout the YAML processing. This means that we can only enable a feature flag globally. If something unexpected happens it can have a large impact cross the instance.
Why this is important?
We want to be able to incrementally enable feature flags whenever possible. Given that the config YAML processing is a core part of CI, we should be able to safely make changes while at the same time limit impacts by enabling the feature flag incrementally.
Proposal
We could use Thread.current
local variable to cache the actor.
Deliverable
PoC or working MVC
References
Edited by Fabio Pitino