Create PORO classes for pipeline execution policy
What does this MR do and why?
This MR introduces PORO classes to provide a structured, object-oriented interface for working with pipeline execution policy content. This refactoring improves code maintainability and type safety when accessing policy configuration data.
Problem: Currently, pipeline execution policy content is accessed directly as hash data structures, which makes the code harder to maintain, test, and understand.
Solution: Create dedicated PORO classes that encapsulate the policy structure and provide clear accessor methods for all policy attributes.
The refactor is split into multiple MRs for each policy types:
-
1️⃣ Create PORO classes for MR approval policy (!209363 - merged) -
2️⃣ Create PORO classes for scan execution policy (!212585 - merged) -
3️⃣ Create PORO classes for pipeline execution policy (!212587)
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #504305