You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.
I know the event filtering is possible, but that's a global setting. It applies to all installed JES instances that are attached to a single control plane.
Is it possible to leverage metadata in triggered events (or some other property) to conditionally execute different JES installs in the same project + service + stage combination?
For example, imagine I have 3 clusters globally all listening for test.triggered in projectA of service1 and environment prod and I wish to only load test on the europe cluster. I might pass in some property like data.test.location and then my JES could filter for:
I know the event filtering is possible, but that's a global setting. It applies to all installed JES instances that are attached to a single control plane.
Is it possible to leverage metadata in triggered events (or some other property) to conditionally execute different JES installs in the same project + service + stage combination?
For example, imagine I have 3 clusters globally all listening for
test.triggered
inprojectA
ofservice1
and environmentprod
and I wish to only load test on theeurope
cluster. I might pass in some property likedata.test.location
and then my JES could filter for:The text was updated successfully, but these errors were encountered: