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
Currently, the Workflow API provisions workflows asynchronously. The API responds immediately with a 200 OK, requiring clients to poll the Workflow Status API to monitor the provisioning status. While this approach enables front-end progress visualization, it adds complexity for automation tools that must implement polling mechanisms.
Certain use cases, such as Machine Learning Commons Remote Model Deployment, benefit from synchronous provisioning, allowing the API to return only when the workflow is completed.
Now, we are adding the wait_for_completion_timeout parameter to allow synchronized calls in three endpoints:
POST /_plugins/_flow_framework/workflow?provision=true
POST /_plugins/_flow_framework/workflow/<workflow_id>/_provision
PUT /_plugins/_flow_framework/workflow/<workflow_id>?reprovision=true
What do you want to do?
Tell us about your request.
Currently, the Workflow API provisions workflows asynchronously. The API responds immediately with a 200 OK, requiring clients to poll the Workflow Status API to monitor the provisioning status. While this approach enables front-end progress visualization, it adds complexity for automation tools that must implement polling mechanisms.
Certain use cases, such as Machine Learning Commons Remote Model Deployment, benefit from synchronous provisioning, allowing the API to return only when the workflow is completed.
Now, we are adding the
wait_for_completion_timeout
parameter to allow synchronized calls in three endpoints:Version: 2.19 and after
What other resources are available?
PR: opensearch-project/flow-framework#990
Issue: opensearch-project/flow-framework#967
The text was updated successfully, but these errors were encountered: