L
Labour Wombat
Summary:
Customers would like the ability to enforce policies only during pipeline creation, and not during subsequent edits or saves. This would allow more targeted governance use cases, such as ensuring specific metadata or tags are set at creation time, without blocking updates to existing pipelines.
Current Behavior:
  • The policy engine currently triggers on "save" events, but does not distinguish between a new pipeline being created and an existing pipeline being edited.
  • The input payload lacks any explicit indicator (e.g., createdAt, isNew, or operation type) to help identify whether the event is a create or an update.
Expected Behavior / Enhancement:
Introduce a way to detect creation events, such as:
  • A field in the policy evaluation input payload (e.g., createdAt, isNew)
  • An event type that distinguishes between CREATE and UPDATE
  • Or alternatively, expose the pipeline’s existing state (if any) as context for comparison
Example of Use Case:
A customer is implementing governance policies for pipeline and would like to enforce certain validations (e.g., required fields, naming conventions, tag presence) only at the time a pipeline is first created, without affecting future edits.
This would prevent policy fatigue and make policies more purpose-driven.
Created by Pedro Mastelaro
·