Follow-up from "Implement saving config content for pipelines"
The following discussion from !21827 (merged) should be addressed:
-
@fabiopitino started a discussion: Can we create a separate issue where we remove the feature flag
ci_root_config_content
in %12.8 if no issues arise?In that issue we can also mention that we can remove assigning
@command.config_content = config.content
and instead usepipeline.pipeline_config.content
in otherCi::Pipeline::Chain::
steps (e.g. inChain::Config::Process
).