`Microsoft.Authorization/roleAssignments` declares support for `2020-10-01-preview`, but does not work with ARM

[anthony-c-martin]

Reported here: Azure/bicep#784 (comment)

Here it's declared in swagger spec:

azure-rest-api-specs/specification/authorization/resource-manager/Microsoft.Authorization/preview/2020-10-01-preview/authorization-RoleAssignmentsCalls.json

Line 231 in 88e7838

"put": {

However there is no manifest configuration for this API version.

[matsest]

Also note that the error message from deployment (se original report above) lists 2021-04-01-preview as a supported version, but this is not listed in docs/suggested from Bicep intellisense.

[anthony-c-martin]

Also note that the error message from deployment (se original report above) lists 2021-04-01-preview as a supported version, but this is not listed in docs/suggested from Bicep intellisense.

Thanks for pointing this out - again this looks like an issue in the swagger - https://github.com/Azure/azure-rest-api-specs/tree/88e7838a09868a51de3894114355c75929847a46/specification/authorization/resource-manager/Microsoft.Authorization/preview contains no 2021-04-01-preview version, but as you mentioned, the service supports it.

@zhenglaizhang should we raise a new issue for this, or would you like to track it under this one?

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @darshanhs90, @AshishGargMicrosoft.

Issue Details

---

Reported here: Azure/bicep#784 (comment)

Here it's declared in swagger spec:

azure-rest-api-specs/specification/authorization/resource-manager/Microsoft.Authorization/preview/2020-10-01-preview/authorization-RoleAssignmentsCalls.json

Line 231 in 88e7838

"put": {

However there is no manifest configuration for this API version.

Author:	anthony-c-martin
Assignees:	-
Labels:	Authorization, Service Attention
Milestone:	-

[ruowan]

I add a service attention label. Maybe service team could take a look.

[dagoroz]

@anthony-c-martin the binaries that support 2020-10-01-preview took longer than expected and publications got de-synced
our team is working to get them published as fast as possible
I will keep this issue open, if others pop up please redirect them here