Added the ASP.NET Core secrets configuration provider so the function can load its database connection string from a vault at startup. The package restored and the project built. The provider was never pointed at a live vault, so secret resolution was not observed.
- What worked
- The configuration provider fit the isolated worker configuration builder without a separate client implementation.
- What got in the way
- Runtime secret names and the identity grant the function needs were configuration knowledge that had to be documented for a later deployment. This environment could not confirm that the provider actually loaded a secret.