[Release] sdk/resourcemanager/authorization/armauthorization/2.0.0

[Alancere]

This release help to fix two issues:

• Read Only Fields in DenyAssignmentProperties and Missing Clients  #18811
• [armauthorization] switch to newer apiversion for RoleDefinitions (dataActions, notDataActions) and RoleAssignments (description support) #18674

[tadelesh]

Wait for .Net authorization GA.

[RickWinter]

v2 releases are painful for customers. We want to keep this on the v1.x path.

[tadelesh]

v2 releases are painful for customers. We want to keep this on the v1.x path.

The breakings contain required param removal, property ref change and operation removal from swagger. I don't think it is possible to make it 1.x.

[mblaschke-daimlertruck]

Any progress here? Is there a way to get this merged in the next days?

[tadelesh]

@RickWinter, @JeffreyRichter, @jhendrixMSFT I've used directive to mitigate most of the breakings. Only one orphan model deletion left. I think it could be ignored regarding it will not break customer. You could see the new generated SDK here and directive here. Could you help to confirm whether we could release it with 1.1.0?

[JeffreyRichter]

Joel & I spoke about this today. Here's where we're at...
It is a reality today that swaggers have bugs, we generate a client and then the swagger gets fixed causing a breaking change in the client (even though the service itself has not changed).

So, if we ship a client V1.0.0 and then the swagger gets fixed, we ship a new client V1.0.1.
Now, let's say an app uses V1.0.1 and also uses another package that depends on V1.0.0 - the app can't build now because V1.0.0 & V1.0.1 can't be compiled together into a single app - this is a very bad place for a customer to be and so we can't do this and put them there.

So, any client library break must be done in a new major version so that the new major and old major can be compiled together into a single app.

Obviously, the best thing for us (service team and SDK teams) to do is to better validate our swaggers and fix bugs before we create and ship client libraries.

[mblaschke]

Any progress here?

[tadelesh]

Any progress here?

We are double confirming with service team and will release the new version soon.

[tadelesh]

@RickWinter Please sign off. .NET has released package-2022-04-01 as stable and we also got confirmation from service team to release Go SDK.

[tadelesh]

Release request: https://github.com/Azure/sdk-release-request/issues/3207

[tadelesh]

All the breaking changes is from this PR and approved in this PR.

1. Function *RoleAssignmentsClient.NewListForResourcePager parameter(s) have been changed from (string, string, string, string, string, *RoleAssignmentsClientListForResourceOptions) to (string, string, string, string, *RoleAssignmentsClientListForResourceOptions)
   New swagger here. Previous swagger here. This operation's path params have been changed.
2. Type of RoleAssignment.Properties has been changed from *RoleAssignmentPropertiesWithScope to *RoleAssignmentProperties
Struct RoleAssignmentPropertiesWithScope has been removed
   New swagger here. Previous swagger here. Properties of RoleAssignment model has been changed.
3. Function *RoleAssignmentsClient.NewListPager has been removed
Struct RoleAssignmentsClientListOptions has been removed
Struct RoleAssignmentsClientListResponse has been removed
   New swagger here. Previous swagger here. An operation has been renamed.
4. Struct PermissionAutoGenerated has been removed
   New swagger here. Previous swagger here. Permission model for RoleDefinitions has been changed to align with other Permission definition.

[tadelesh]

@jhendrixMSFT @RickWinter @JeffreyRichter I list all the breakings and please help to review.

Jeff and Joel all approved the breaking changes. Release to unblock the customers.