Replies: 1 comment 1 reply
-
This project helped me to undertstand some of the internals and solve my issue |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone 🙂,
I am trying to write integration with Aspire and following the article on https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/testing.
The
DistributedApplicationTestingBuilder
wraps theDistributedApplicationBuilder
of the Aspire app host. This allows to spin up the orchestrator before running the tests.I slightly changed the configuration of the orchestrator to use secrets for some of the required credentials. I don't want to have them in the code and visible on my GitHub repositories.
The plan is to use the .NET Secret Manager to inject them for my development environment and Azure KeyVault or any other type of server ingestion mechanism in the production environments.
The
DistributedApplicationTestingBuilder
doesn't allow to modify the configuration.The simple solution is for the test environment to inject the same environment variables.
I was wondering if there is a way to modify the configuration before building the host:
Is there a way for the test runner to launch a different profile for the Aspire app host?
Thanks in advance 🙂
Beta Was this translation helpful? Give feedback.
All reactions