Joel Hendrix

We definitely need `go test ./...` from the `azblob` directory to work.

The packages under `/services` are from the legacy SDK and no longer updated. Can you try module `github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute/v3`, I believe this has the content you're looking for.

I believe this is the API you want. https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/containerservice/armcontainerservice/v2#ManagedClustersClient.Get Part of the returned model is [`ManagedClusterProperties`](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/containerservice/armcontainerservice/v2#ManagedClusterProperties) which has field `KubernetesVersion`

@benbp I've not seen a CLA notification like this before. Is this new?

I know we had talked about naming this `NewServiceClient()` however I didn't for the following reasons. - We have this same pattern for the specialized clients ([example](https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/storage/azblob/appendblob/client.go#L91-L92)) - The method...

In my mind, this method, and the `BlobClient()` method cited earlier, are more like casts than client ctors (the latter one certainly is). Framed like this, I think it's not...

It appears that the API is incomplete. Since the `Setting` with the `ETag` isn't passed to the API, the condition can never be evaluated (compare this to the [.NET implementation](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/appconfiguration/Azure.Data.AppConfiguration/src/ConfigurationClient.cs#L664))....

We could add a feature that, when `PollingDuration < 0`, the policy doesn't wait for the terminal registration state. Still need to decide how best to surface when the state...

Thinking about this a bit more. The RP registration code is just copied from the [`armresources`](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/resources/armresources#ProvidersClient.Register) module. It might be best to simply disable the policy and roll your own...

The official Azure policy is that for error responses, the only parts that are contractual are the service error code and the HTTP status code; this is why we only...