Skip to content

Commit

Permalink
Revert changes to workflow steps. Users can't use these new step types
Browse files Browse the repository at this point in the history
Signed-off-by: Daniel Widdis <[email protected]>
  • Loading branch information
dbwiddis committed Jul 16, 2024
1 parent 113d180 commit e6b48ba
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 3 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -6,3 +6,4 @@ Gemfile.lock
.idea
*.iml
.jekyll-cache
.project
3 changes: 0 additions & 3 deletions _automating-configurations/workflow-steps.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,8 @@ The following table lists the workflow step types. The `user_inputs` fields for
|`delete_agent` |[Delete Agent API]({{site.url}}{{site.baseurl}}/ml-commons-plugin/) |Deletes an agent. |
|`create_tool` |No API | A special-case non-API step encapsulating the specification of a tool for an agent in the ML Commons Agent Framework. These will be listed as `previous_node_inputs` for the appropriate register agent step, with the value set to `tools`. |
|`create_index`|[Create Index]({{site.url}}{{site.baseurl}}/api-reference/index-apis/create-index/) | Creates a new OpenSearch index. The inputs include `index_name`, which should be the name of the index to be created, and `configurations`, which contains the payload body of a regular REST request for creating an index.
|`delete_index`|[Delete Index]({{site.url}}{{site.baseurl}}/api-reference/index-apis/delete-index/) | Deletes an OpenSearch index. The inputs include `index_name`, which should be the name of the index to be deleted.
|`create_ingest_pipeline`|[Create Ingest Pipeline]({{site.url}}{{site.baseurl}}/ingest-pipelines/create-ingest/) | Creates or updates an ingest pipeline. The inputs include `pipeline_id`, which should be the ID of the pipeline, and `configurations`, which contains the payload body of a regular REST request for creating an ingest pipeline.
|`delete_ingest_pipeline`|[Delete Ingest Pipeline]({{site.url}}{{site.baseurl}}/ingest-pipelines/delete-ingest/) | Deletes an ingest pipeline. The inputs include `pipeline_id`, which should be the ID of the pipeline to delete.
|`create_search_pipeline`|[Create Search Pipeline]({{site.url}}{{site.baseurl}}/search-plugins/search-pipelines/creating-search-pipeline/) | Creates or updates a search pipeline. The inputs include `pipeline_id`, which should be the ID of the pipeline, and `configurations`, which contains the payload body of a regular REST request for creating a search pipeline.
|`delete_search_pipeline`|[Delete Search Pipeline]({{site.url}}{{site.baseurl}}/search-plugins/search-pipelines/deleting-search-pipeline/) | Deletes a search pipeline. The inputs include `pipeline_id`, which should be the ID of the pipeline to delete.
|`reindex`|[Reindex]({{site.url}}{{site.baseurl}}/api-reference/document-apis/reindex/) | The reindex document API operation lets you copy all or a subset of your data from a source index into a destination index. The input includes source_index, destination_index, and the following optional parameters from the document reindex API: `refresh`, `requests_per_second`, `require_alias`, `slices`, and `max_docs`. For more information, see [Reindexing considerations](#reindexing-considerations).

## Reindexing considerations
Expand Down

0 comments on commit e6b48ba

Please sign in to comment.