Hi Folks, are there any best practices for handlin...
# ask-metaflow
c
Hi Folks, are there any best practices for handling prod/dev external events in a Metaflow + Argo Workflows setup? I'm aware that
@project()
works nicely with
@trigger_on_finish()
because it operates within the scope of a flow and so is branch/namespace aware, but the
@trigger()
option for external events doesn't have any of the branch/namespace protections AFAIK. I would prefer to avoid users having to remember to update environment prefixes in triggers when they deploy to argo e.g.
@trigger(dev_foo)
and
@trigger(prod_foo)
Any paved paths here?
To prevent any DenverCoder9. I've resolved this after finding a custom decorator example in the Outerbounds GitHub. A few minor tweaks to make this work for my exact use case, but this essentially solves the problem I described above. namespaced_events