Weidong Xu

Yes, I think it makes sense. If SDK is still retrying, it should not log an ERROR. Do you have a call stack in log? I am getting problem when...

resourcemanager sanitizer mostly here https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-test/src/main/java/com/azure/resourcemanager/test/ResourceManagerTestProxyTestBase.java#L439-L480 a few module would add a few more, e.g. https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-containerregistry/src/test/java/com/azure/resourcemanager/containerregistry/RegistryTest.java#L28-L33

We are actually fine with `@liveOnly`. If we upgrade api-version of a service, we generally require dev to re-run them as LIVE or RECORD, as there is no promise that...

@v-hongli1 Search `@LiveOnly` in sdk/resourcemanager, and see if you can remove it, record, and pass playback. Please do it one module at a time. Make sure your branch is after...

@ShuratCode Could you list the version of azure-core and azure-core-management in project? E.g. `mvn dependency:list`. Please make sure the azure-core and azure-core-management is around these versions (if you uses 2.34.0)...

The reason top of my mind, is that SDK itself does not send any request to storage account endpoint. Hence there is no need to build the scope to storage...

KeyVault is because SDK do create the client (sharing the same pipeline) to access KeyVault endpoint https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-keyvault/src/main/java/com/azure/resourcemanager/keyvault/implementation/VaultImpl.java#L91-L102 (hence the pipeline need to apply the scope for KeyVault)

If you need to share the pipeline with other applications (e.g. those need access StorageAcount), you may want to plugin a slightly different `AuthenticationPolicy` based on [this impl](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-resources/src/main/java/com/azure/resourcemanager/resources/fluentcore/policy/AuthenticationPolicy.java). The code...

OK, we will take a look, but probably not at high priority as it not affect most customers. One may not really need to share the HttpPipeline. The usual suggestion...

If we have `extends`, could it be `enum Closed { a, b }` for values that never change. `union CurrentValues extends string {"a", "b"}` for values that is exhaustive currently,...