You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a way to start over with a new Context - optionally keeping telemetry spans - when calling into other crates' methods like azure_identity. We don't want, for example, Retry options for Key Vault clients to pass through to DefaultAzureCredential. See Go for more context and solution concept ideas.
The text was updated successfully, but these errors were encountered:
One idea might be to define a trait that anything added to the Context's HashMap has to implement that says whether it's durable. A client or token credential can specify whether non-durable context should be dropped when crossing boundaries. This would allow spans through.
To actually trace, like Go and some other languages, a non-durable context object could be the trace listener (tracer) such that a user can specify tracing for one client but not another.
We need a way to start over with a new
Context
- optionally keeping telemetry spans - when calling into other crates' methods likeazure_identity
. We don't want, for example,Retry
options for Key Vault clients to pass through toDefaultAzureCredential
. See Go for more context and solution concept ideas.The text was updated successfully, but these errors were encountered: