Can I create triggers in the definitions section of the

prefect.yaml

file and reuse the same trigger across multiple deployments? Or do I have to write out the trigger for each deployment?

you do not have to rewrite - specifying a trigger in the prefect.yaml will essentially be a default for all applied deployments.

Oh I see. Then I can overwrite it on specific deployments if I choose to?

precisely

@Will Raphaelson I am so excited for this + webhooks! Thanks!

hell yeah! me too. the engineers really crushed it on the webhook implementation IMO.

Is there a way to set the default and then just put no default on a specific deployment? An empty list on the deployment?

havent done it but i have reasonably high confidence that’s the correct spelling.

@Will Raphaelson I am having issues with this:

triggers:
  - enabled: true
    match:
      prefect.resource.id: prefect.flow-run.*
    expect:
      - prefect.flow-run.Completed
    match_related:
      prefect.resource.name: falcon_cap_iq_dbt_deployment
      prefect.resource.role: deployment

I have this entry in my

prefect.yaml

at the top and a list of deployments in the file that have no trigger specification. After deploying them, none of them had this trigger attached to them.

Per our DMs, i was wrong, and here’s the isuse to watch 🙂 https://github.com/PrefectHQ/prefect/issues/10223