[BUG] Microsoft.Maps @ 2023-06-01 - PUT and DELETE operations for Accounts should be marked as LRO

[stephybun]

API Spec link

azure-rest-api-specs/specification/maps/resource-manager/Microsoft.Maps/stable/2023-06-01/maps-management.json

Lines 81 to 93 in 89fc547

	"responses": {
	"200": {
	"description": "The Account was successfully updated.",
	"schema": {
	"$ref": "#/definitions/MapsAccount"
	}
	},
	"201": {
	"description": "The Account was successfully created.",
	"schema": {
	"$ref": "#/definitions/MapsAccount"
	}
	},

API Spec version

2023-06-01

Describe the bug

The PUT and DELETE methods in the spec for Maps are not marked as Long Running Operations

However creating a Maps Account returns a provisioningState of Updating

...
"properties": {
    "uniqueId": "36b85746-cbda-45e5-8f60-7090a13ccc3c",
    "provisioningState": "Updating",
...

And attempting to delete results in the following error:

unexpected status 409 (409 Conflict) with error: InvalidProvisoningState: The current provisioningState must transition to a terminal state before the resource can be updated.

I believe these operations should be Long Running operations and return an async URL in the header that we can poll on to know when a Maps Account resource is ready to be updated or deleted.

Expected behavior

When creating a Maps Account I should receive an async operation URL in the header that will allow me to poll the provisioning status of the resource.

Actual behavior

Creating a Maps Account returns a 201 with no async operation operation URL in the header for us to poll on. Issuing an update to the account or a delete right after results in a 409 error.

Reproduction Steps

Create a Map Account then issue an update or a delete immediately afterwards.

Environment

No response

[v-jiaodi]

@gigigoo0 Can you help take a look？

[gigigoo0]

Will take a look.