Adding tag-based enforcement for input sets and triggers through OPA.
long-term
M
Mild Crab
United Airlines would like to request support for tag-based enforcement on Input Sets and Triggers using OPA policies. Today, OPA can evaluate pipeline-level metadata, but tags applied directly to Input Sets and Triggers are not exposed in the policy payload. Enabling this capability would allow us to enforce governance rules such as restricting which input sets can be used for certain deployments, validating trigger categorization, and ensuring consistent tagging practices across teams. This enhancement would significantly strengthen governance, compliance, and automation within our pipelines.
Log In
a
abhijit.pujare
marked this post as
long-term
a
abhijit.pujare
Thank you for submitting the feature request. We’ll added this request to our planning process and will update you once we have added it to our roadmap and have a timeline to share.