In conforma/policy#1268, I updated the conforma policies to support accepting multiple values for pipeline_intention so that we can use different rulesets for a "staging" release vs a "production" release.
My question now is: what is the best way to plumb that value from the ReleasePlanAdmission to the managed pipelinerun?
- I could put it in
.spec.data.intention and then access it like a normal data key in the verify-enterprise-contract task.
- Or, I see that there's a
enterpriseContractExtraRuleData param on all of the managed pipelines that defaults to pipeline_intention=release. It looks like what I want to do is set that to "production" or "staging" based on something in the RPA.
But, when I look in the release-service's controller code, I think that nothing is actually providing that param at the moment and the default is always used.
Is that the right path to implement? Modify the release-service controller to get extra rule data from the RPA and provide it to each pipelineRun.
In conforma/policy#1268, I updated the conforma policies to support accepting multiple values for pipeline_intention so that we can use different rulesets for a "staging" release vs a "production" release.
My question now is: what is the best way to plumb that value from the ReleasePlanAdmission to the managed pipelinerun?
.spec.data.intentionand then access it like a normal data key in the verify-enterprise-contract task.enterpriseContractExtraRuleDataparam on all of the managed pipelines that defaults topipeline_intention=release. It looks like what I want to do is set that to "production" or "staging" based on something in the RPA.But, when I look in the release-service's controller code, I think that nothing is actually providing that param at the moment and the default is always used.
Is that the right path to implement? Modify the release-service controller to get extra rule data from the RPA and provide it to each pipelineRun.