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
As the pipeline execution operation is an async operation, the trigger from pipeline service should not directly communicate with executor service otherwise it will unnecessarily pause the intermediate services and client. Hence, as the architecture depicts, the pipeline service should put the pipeline's definition as a message in a queue and the executor service will consume it.
As part of this task, create the configuration from pipeline service's side. Introduce a new feature flag and if it's enabled then pipeline service should put the requested pipeline's definition onto the message queue, if it's disabled keep the existing workflow.
Benefit hypothesis
Architecture compliant implementation from pipeline service's side.
Activity