Hello, I am working to integrate metaflow and Argo using events. I have a webhook that captures events from running flows and forwards them on to other services and I also want external services to be able to trigger workflows via events. So far, I have 2 webhooks, one that is configured as the

METAFLOW_ARGO_EVENTS_INTERNAL_WEBHOOK_URL

for sending events from the flows to the outside world and another that is exposed for other services to push events into argo. Adding the

@trigger

decorator and trying to deploy the workflow returns an error

An Argo Event name hasn't been configured for your deployment yet. Please see this article for more details on event names - <https://argoproj.github.io/argo-events/eventsources/naming/>. It is very likely that all events for your deployment share the same name. You can configure it by executing `metaflow configure kubernetes` or setting METAFLOW_ARGO_EVENTS_EVENT in your configuration. If in doubt, reach out for support at <http://chat.metaflow.org>

My question is: If I configure the

METAFLOW_ARGO_EVENTS_EVENT

will that interfere with the existing outgoing events data flow? Alternatively, I could setup Sensors to trigger each flow, but I was hoping to keep this configuration piece in the metaflow realm.