Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC] Introducing Sync Execution for Workflow Provisioning: Adding wait_for_completion_timeout #9116

Closed
1 of 4 tasks
junweid62 opened this issue Jan 27, 2025 · 0 comments · Fixed by #9138
Closed
1 of 4 tasks
Assignees
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. v2.19.0

Comments

@junweid62
Copy link
Contributor

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

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:

  1. POST /_plugins/_flow_framework/workflow?provision=true
  2. POST /_plugins/_flow_framework/workflow/<workflow_id>/_provision
  3. PUT /_plugins/_flow_framework/workflow/<workflow_id>?reprovision=true

Version: 2.19 and after

What other resources are available?
PR: opensearch-project/flow-framework#990
Issue: opensearch-project/flow-framework#967

@Naarcha-AWS Naarcha-AWS added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. v2.19.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants