Hi! I have a question on integrating with Argo Events. When I deploy a new template that uses the

@trigger

decorator it creates a new sensor in the Argo Sensors. How can I make it so that it re-uses one of the sensors which are already defined (ie I have a sensor that lists SQS as the resource, so I would like my new workflow to be triggered when a new message comes in the SQS queue).

@handsome-ocean-90256 currently a sensor maps 1:1 to a deployed flow and is auto-generated. It is allocated very few resources (100m vCPUs and 0.25 GB RAM)

yeah I guess there are 2 options, to either have a script running that listens to sqs messages and passes them on or to create our own sensor as part of the deployment that has the source defined as sqs.