Tim Hess

We have a CI build of packages that should have this issue fixed available [here](https://dev.azure.com/SteeltoeOSS/Steeltoe/_build/results?buildId=29581&view=artifacts&pathAsName=false&type=publishedArtifacts) if you want to try them out. We can have them available in a nuget...

Package version `3.2.9-29610` is available now in the dev feed, which is accessible with a nuget.config that looks like this: ```xml ```

How are tracing properties useful on these items? These interactions are typically called in the background rather than as a part of any distributed interaction.

I just tested this on Steeltoe v4 with OpenTelemetry configured to instrument HttpClient, and all outbound requests are recorded. It does not appear to make a difference when viewing the...

This would also be another opportunity to review the level at which Steeltoe is logging... The second and third entries should maybe be debug/trace instead of info

> Thanks for diving into this. I haven't tested the changes, assuming you did. Yes, but also because https://github.com/SteeltoeOSS/Samples/pull/391 works with the same set of sample apps and I was...

It seems like there's a trend towards using a managed identity for signing, and I think these warnings are likely related since we're interacting with a vault in Azure without...

Update from the foundation... Managed identity _is_ coming, but the timeline for us to migrate is unclear. We can continue with this solution for now

After further investigation, it looks like while the variables could be used in our test environment, they are not actually guaranteed to be in any way related to a valid...

All versions of all packages except those versioned `2.5.5`, `3.2.8` and `4.0.0-beta1` are now unlisted