InvalidResourceType when creating new RBAC assignment using SDK

[DamirZelenic]

Bug Report

• import path of package in question
  github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization"

• SDK version e.g. master, latest, 18.1.0
  v0.3.0

• output of go version
  go version go1.17.6 darwin/arm64

• What happened?
  When trying to create new RBAC role assignment using Create method I got:

RESPONSE 404: 404 Not Found
ERROR CODE: InvalidResourceType
{
  "error": {
    "code": "InvalidResourceType",
    "message": "The resource type 'roleAssignments' could not be found in the namespace 'Microsoft.Authorization' for api version '2020-10-01-preview'. The supported api-versions are '2014-04-01-preview,2014-07-01-preview,2014-10-01-preview,2015-05-01-preview,2015-06-01,2015-07-01,2016-07-01,2017-05-01,2017-09-01,2017-10-01-preview,2018-01-01-preview,2018-07-01,2018-09-01-preview,2018-12-01-preview,2019-04-01-preview,2020-03-01-preview,2020-04-01-preview,2020-08-01-preview,2021-04-01-preview'."
  }
}

• What did you expect or want to happen?
  Expect result like:

2022/02/15 11:45:19 Response result: armauthorization.RoleAssignmentsClientCreateResult{RoleAssignment:armauthorization.RoleAssignment{Properties:(*armauthorization.RoleAssignmentProperties)(0x14000202120), ID:(*string)(0x14000552710), Name:(*string)(0x14000552730), Type:(*string)(0x14000552720)}}

As error suggests there is unsupported api version in
azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization@v0.3.0/zz_generated_roleassignments_client.go

line 87:

reqQP.Set("api-version", "2020-10-01-preview")

changing it to supported version, for example:

reqQP.Set("api-version", "2020-08-01-preview")

produces expected result.

• How can we reproduce it?

rbacClient := armauthorization.NewRoleAssignmentsClient(subscriptionID, cred, nil)
	rbacres, err := rbacClient.Create(ctx,
		scope,
		uuid, //"<role-assignment-name>" must be unique
		armauthorization.RoleAssignmentCreateParameters{
			Properties: &armauthorization.RoleAssignmentProperties{
				PrincipalID:      to.StringPtr(principalID),
				PrincipalType:    armauthorization.PrincipalType("User").ToPtr(),
				RoleDefinitionID: to.StringPtr(roleDefID),
			},
		},
		nil)

[ArcturusZhang]

Hi @DamirZelenic thanks for this issue and sorry for the inconvenience!

We will confirm this with the corresponding service team to see if this api-version has been deployed to all the regions. Stay tuned.
As a workaround, we could downgrade the api-version in this package to 2020-08-01-preview to ensure everything could work properly here.

Also could you please also share the location/region (if any) and cloud you are using when deploying the role assignment?

[ghost]

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

Issue Details

---

Bug Report

• import path of package in question
  github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization"

• SDK version e.g. master, latest, 18.1.0
  v0.3.0

• output of go version
  go version go1.17.6 darwin/arm64

• What happened?
  When trying to create new RBAC role assignment using Create method I got:

RESPONSE 404: 404 Not Found
ERROR CODE: InvalidResourceType
{
  "error": {
    "code": "InvalidResourceType",
    "message": "The resource type 'roleAssignments' could not be found in the namespace 'Microsoft.Authorization' for api version '2020-10-01-preview'. The supported api-versions are '2014-04-01-preview,2014-07-01-preview,2014-10-01-preview,2015-05-01-preview,2015-06-01,2015-07-01,2016-07-01,2017-05-01,2017-09-01,2017-10-01-preview,2018-01-01-preview,2018-07-01,2018-09-01-preview,2018-12-01-preview,2019-04-01-preview,2020-03-01-preview,2020-04-01-preview,2020-08-01-preview,2021-04-01-preview'."
  }
}

• What did you expect or want to happen?
  Expect result like:

2022/02/15 11:45:19 Response result: armauthorization.RoleAssignmentsClientCreateResult{RoleAssignment:armauthorization.RoleAssignment{Properties:(*armauthorization.RoleAssignmentProperties)(0x14000202120), ID:(*string)(0x14000552710), Name:(*string)(0x14000552730), Type:(*string)(0x14000552720)}}

As error suggests there is unsupported api version in
azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization@v0.3.0/zz_generated_roleassignments_client.go

line 87:

reqQP.Set("api-version", "2020-10-01-preview")

changing it to supported version, for example:

reqQP.Set("api-version", "2020-08-01-preview")

produces expected result.

• How can we reproduce it?

rbacClient := armauthorization.NewRoleAssignmentsClient(subscriptionID, cred, nil)
	rbacres, err := rbacClient.Create(ctx,
		scope,
		uuid, //"<role-assignment-name>" must be unique
		armauthorization.RoleAssignmentCreateParameters{
			Properties: &armauthorization.RoleAssignmentProperties{
				PrincipalID:      to.StringPtr(principalID),
				PrincipalType:    armauthorization.PrincipalType("User").ToPtr(),
				RoleDefinitionID: to.StringPtr(roleDefID),
			},
		},
		nil)

Author:	DamirZelenic
Assignees:	ArcturusZhang
Labels:	question, Authorization, Service Attention, Mgmt, customer-reported
Milestone:	-

[DamirZelenic]

Hi @ArcturusZhang
It is default AzureCloud. Subscription and RBAC assignment doesn't have any specific region?
Subscription location placement id:

"LocationPlacementId": "Public_2014-09-01"

In error message I see newer api being available "...2020-08-01-preview,2021-04-01-preview", only 10-01 is missing.
I can share Role Assignment Id if needed.

[ArcturusZhang]

Hi @ArcturusZhang It is default AzureCloud. Subscription and RBAC assignment doesn't have any specific region? Subscription location placement id:

"LocationPlacementId": "Public_2014-09-01"

In error message I see newer api being available "...2020-08-01-preview,2021-04-01-preview", only 10-01 is missing. I can share Role Assignment Id if needed.

Please share that as well if possible. Thank you!

[github-actions]

Hi @DamirZelenic. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[github-actions]

Hi @DamirZelenic, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!