Jeff Fisher
Jeff Fisher
> Makes sense to me! Just to help my understanding, logging policy will not be applied to our default auth policy? Sort of, the way this works is we aren't...
@petrsvihlik can you help route this?
/cc @anjulgarg too
Error running the docker container while consuming azure identity module with caching option enabled
@KarishmaGhiya is the expert here, but can I confirm that you enabled the plugin by calling `useIdentityPlugin`? ```ts const { useIdentityPlugin } = require("@azure/identity"); const { cachePersistencePlugin } = require("@azure/identity-cache-persistence");...
One determinant could be if any of these options/properties show up in existing README snippets or samples. If not, I think we could argue a minor bump is sufficient.
The only downside of being pedantic in this case appears to be policy around supporting major versions for an extra year, so we'd increase our dev costs each time we...
Seems like we have consensus. One question though: does the answer change if the sdk in question did work to not expose `_response`, as ACS did?
Since `core-http` works on `WebResourceLike`s and `core-rest-pipeline` works on `PipelineRequest`s, there are some differences: ```ts export interface WebResourceLike { // shared members are omitted clone(): WebResourceLike; //removed decompressResponse?: boolean; //...
> > what do you do if maxRedirects is also specified? Maybe we can throw an Error > > We can document the older option as being kept for backward...
> For the `clone()` method, is the assumption of object identity because the pipeline stores a ref to the request and assumes it is the same one that is ultimately...