For AI integration tests, use config including user secrets #5706
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was getting tired of having to remember to set environment variables and restart VS whenever I wanted to run the integration tests. We were also a bit out of line with our recommendations in using
GetEnvironmentVariable
directly instead of going through theIConfiguration
abstraction which allows for multiple configuration sources.With this change, you can set your config just once using
dotnet user-secrets
and it will be stored in your user profile in a way that's scoped to this repo. Instructions added to readme file.Alternatively you can continue using environment variables (though the names have changed to match .NET config naming conventions).