Skip to content

[BUG] Azure.ResourceManager.Logic.LogicWorkflowResource.UpdateAsync always returns 400 BadRequest #33246

@jdefesche1

Description

@jdefesche1

Library name and version

Azure.ResourceManager.Logic 1.0.0

Describe the bug

When I call UpdateAsync irrespective of having updated the Data.Definition, it returns a bad request (Resource Definition is invalid). I've used fiddler to capture traffic using the deprecated package (Microsoft.Azure.Management.Logic) when calling UpdateAsync. Repeated the process for Azure.ResourceManager.Logic but there I see no body.

See the document containing the Fiddler traces:
Azure.ResourceManager.Logic bug MS.docx

Expected behavior

When calling LogicWorkflowResource.UpdateAsync the json representation of the definition should be included in the request.

Actual behavior

The exception I get while debugging is
badrequest

Reproduction Steps

  1. Get a workflow using GetAsync()
  2. Update the workflow using UpdateAsync()

Environment

  • Visual Studio 2022 (64 bit) 17.3.6
  • Windows server 2022 version 21H2 OS Build 20348.887
  • project is class library .net standard 2.0

Metadata

Metadata

Assignees

Labels

Logic AppMgmtThis issue is related to a management package.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe 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