Skip to content

Microsoft.Logic Workflows Update API lacks parameter to populate the request body #18132

Open
@dmartin-r7

Description

@dmartin-r7

Workflow parameter is not present in the latest API version, so the request body is never populated in update calls.

SDK is generated by swagger;

In the preview of the 2018-07-01 version, the parameters are normally defined;
fyi:

"patch": {
"tags": [
"Workflows"
],
"operationId": "Workflows_Update",
"description": "Updates a workflow.",
"x-ms-examples": {
"Patch a workflow": {
"$ref": "./examples/Workflows_Update.json"
}
},
"parameters": [
{
"$ref": "#/parameters/subscriptionId"
},
{
"name": "resourceGroupName",
"description": "The resource group name.",
"in": "path",
"required": true,
"type": "string"
},
{
"name": "workflowName",
"description": "The workflow name.",
"in": "path",
"required": true,
"type": "string"
},
{
"$ref": "#/parameters/api-version"
},
{
"name": "workflow",
"description": "The workflow.",
"in": "body",
"required": true,
"schema": {
"$ref": "#/definitions/Workflow"
}
}
],

Parameters are missing in the stable version of 2019-05-01
fyi:

"patch": {
"tags": [
"Workflows"
],
"operationId": "Workflows_Update",
"description": "Updates a workflow.",
"x-ms-examples": {
"Patch a workflow": {
"$ref": "./examples/Workflows_Update.json"
}
},
"parameters": [
{
"$ref": "#/parameters/subscriptionId"
},
{
"name": "resourceGroupName",
"description": "The resource group name.",
"in": "path",
"required": true,
"type": "string"
},
{
"name": "workflowName",
"description": "The workflow name.",
"in": "path",
"required": true,
"type": "string"
},
{
"$ref": "#/parameters/api-version"
}

It is recommended to submit your new issue to https://github.com/Azure/azure-rest-api-specs/issues

Originally posted by @Wzb123456789 in Azure/azure-sdk-for-python#23160 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Logic AppService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions