* Add flow framework documentation Signed-off-by: Fanit Kolchina <[email protected]> * Tech review comments Signed-off-by: Fanit Kolchina <[email protected]> * Update _automating-workflows/api/create-workflow.md Co-authored-by: Owais Kazi <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Add callout of edges being optional Signed-off-by: Fanit Kolchina <[email protected]> * Add unregister to word list Signed-off-by: Fanit Kolchina <[email protected]> * Add registering local pretrained and custom models Signed-off-by: Fanit Kolchina <[email protected]> * Apply suggestions from code review Co-authored-by: Melissa Vagi <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Apply suggestions from code review Co-authored-by: Melissa Vagi <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Update _automating-workflows/api/deprovision-workflow.md Co-authored-by: Melissa Vagi <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Update _automating-workflows/workflow-steps.md Co-authored-by: Melissa Vagi <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Apply suggestions from code review Co-authored-by: Melissa Vagi <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Added Flow Framework plugin to Vale Signed-off-by: Fanit Kolchina <[email protected]> * Apply suggestions from code review Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * More editorial comments Signed-off-by: Fanit Kolchina <[email protected]> * Update _automating-workflows/api/get-workflow-status.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Update _automating-workflows/api/get-workflow-status.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Add note about provisioning Signed-off-by: Fanit Kolchina <[email protected]> * Update _automating-workflows/index.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * Update _automating-workflows/workflow-steps.md Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> * More editorial comments Signed-off-by: Fanit Kolchina <[email protected]> * Removed code font from headings Signed-off-by: Fanit Kolchina <[email protected]> * Add agent documentation links Signed-off-by: Fanit Kolchina <[email protected]> * Add experimental label and more links Signed-off-by: Fanit Kolchina <[email protected]> * Add sample templates link Signed-off-by: Fanit Kolchina <[email protected]> * Added a tracking issue to warning Signed-off-by: Fanit Kolchina <[email protected]> --------- Signed-off-by: Fanit Kolchina <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> Co-authored-by: Owais Kazi <[email protected]> Co-authored-by: Melissa Vagi <[email protected]> Co-authored-by: Nathan Bower <[email protected]>
1.8 KiB
layout, title, parent, nav_order
| layout | title | parent | nav_order |
|---|---|---|---|
| default | Get workflow steps | Workflow APIs | 50 |
Get workflow steps
This is an experimental feature and is not recommended for use in a production environment. For updates on the progress of the feature or if you want to leave feedback, see the associated GitHub issue.
{: .warning}
OpenSearch validates workflows by using the validation template that lists the required inputs, generated outputs, and required plugins for all steps. For example, for the register_remote_model step, the validation template appears as follows:
{
"register_remote_model": {
"inputs": [
"name",
"connector_id"
],
"outputs": [
"model_id",
"register_model_status"
],
"required_plugins": [
"opensearch-ml"
]
}
}
The Get Workflow Steps API retrieves this file.
Path and HTTP methods
GET /_plugins/_flow_framework/workflow/_steps
Example request
GET /_plugins/_flow_framework/workflow/_steps
{% include copy-curl.html %}
Example response
OpenSearch responds with the validation template containing the steps. The order of fields in the returned steps may not exactly match the original JSON but will function identically.
To retrieve the template in YAML format, specify Content-Type: application/yaml in the request header:
curl -XGET "http://localhost:9200/_plugins/_flow_framework/workflow/8xL8bowB8y25Tqfenm50" -H 'Content-Type: application/yaml'
To retrieve the template in JSON format, specify Content-Type: application/json in the request header:
curl -XGET "http://localhost:9200/_plugins/_flow_framework/workflow/8xL8bowB8y25Tqfenm50" -H 'Content-Type: application/json'