-
Notifications
You must be signed in to change notification settings - Fork 503
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
Document reprovision param for Update Workflow API #8172
Changes from 4 commits
79ae861
cfb2862
bfe6e58
67eb5ac
cf55dbc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -58,7 +58,7 @@ | |
``` | ||
{% include copy-curl.html %} | ||
|
||
You cannot update a full workflow once it has been provisioned, but you can update fields other than the `workflows` field, such as `name` and `description`: | ||
In a workflow that has not been provisioned, you can update fields other than the `workflows` field. For example, you can update the `name` and `description` fields as follows: | ||
|
||
```json | ||
PUT /_plugins/_flow_framework/workflow/<workflow_id>?update_fields=true | ||
|
@@ -72,12 +72,25 @@ | |
You cannot specify both the `provision` and `update_fields` parameters at the same time. | ||
{: .note} | ||
|
||
If a workflow has been provisioned, you can update and reprovision the full template: | ||
Check failure on line 75 in _automating-configurations/api/create-workflow.md GitHub Actions / style-job
|
||
|
||
```json | ||
PUT /_plugins/_flow_framework/workflow/<workflow_id>?reprovision=true | ||
{ | ||
<updated complete template> | ||
} | ||
``` | ||
|
||
You can add new steps to the workflow but not delete them. Only steps for index settings, search pipelines, and ingest pipelines are currently supported for updating. | ||
dbwiddis marked this conversation as resolved.
Show resolved
Hide resolved
|
||
{: .note} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The {: .note} is not producing anything specific in markdown, can we remove? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see, I am okay with it then There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I anticipate we'll make this particular paragraph more detailed and link to a whole separate page (like the use case templates) for the remainder of the feature, so just trying to add the minimum this time. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Correct, the {: .note} renders as a blue callout. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Doesn't render in GitHub but does render on the doc site. |
||
|
||
The following table lists the available query parameters. All query parameters are optional. User-provided parameters are only allowed if the `provision` parameter is set to `true`. | ||
|
||
| Parameter | Data type | Description | | ||
| :--- | :--- | :--- | | ||
| `provision` | Boolean | Whether to provision the workflow as part of the request. Default is `false`. | | ||
| `update_fields` | Boolean | Whether to update only the fields included in the request body. Default is `false`. | | ||
| `reprovision` | Boolean | Whether to reprovision the entire template if it has already been provisioned. A complete template must be provided in the request body. Default is `false`. | | ||
Check failure on line 93 in _automating-configurations/api/create-workflow.md GitHub Actions / style-job
|
||
| `validation` | String | Whether to validate the workflow. Valid values are `all` (validate the template) and `none` (do not validate the template). Default is `all`. | | ||
| User-provided substitution expressions | String | Parameters matching substitution expressions in the template. Only allowed if `provision` is set to `true`. Optional. If `provision` is set to `false`, you can pass these parameters in the [Provision Workflow API query parameters]({{site.url}}{{site.baseurl}}/automating-configurations/api/provision-workflow/#query-parameters). | | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I expect this section to create a merge conflict when #8171 is merged. This section should go above that new content as it's directly related to updating. I'll resolve conflicts when the time comes.