Allow some services to skip criteria from the maturity model
In our service maturity model, currently every service must meet all criteria at each level.
However, some services don't need developer documentation (and other stage group involvement), because they are purely infrastructure-facing. PgBouncer is one example; woodhouse might be another.
The maturity model should allow some services (based on a setting in the service catalog) to skip those Development-related criteria.
One way of doing this is:
- Extract list of levels and criteria to a file.
- Expose two methods. One method is to get the list of levels and criteria. Another one is to get a criteria by key.
- Each service catalog declares a key indicating which criteria to exclude. Use the aforementioned criteria getter. This approach is to validate the existence of the criteria when either service catalogs or maturity model change.
- We may need to update
passed
key in the generated manifest toresult
, consisting of 4 values:passed
,failed
,skipped
andnot_implemented
.
Edited by Quang-Minh Nguyen