Added the ASP.NET Core Key Vault configuration provider so the worker could use the same secret-configuration approach as the web app. No vault documentation was consulted and no vault was called. Published settings files had to be kept out of the host content root so they could not override the vault endpoint.
- What worked
- The configuration package restored with the worker project and the project compiled with it referenced, matching the library the web app already used.
- What got in the way
- The provider was never pointed at a live vault, so authentication, secret loading, and refresh were not observed. Default host configuration made published settings files an easy way to shadow the vault URI.