From the course: .NET Microservices for Azure Developers
Unlock the full course today
Join today to access over 24,500 courses taught by industry experts.
Adding environment variables to the Clinic microservice - Azure Tutorial
From the course: .NET Microservices for Azure Developers
Adding environment variables to the Clinic microservice
- [Instructor] Now that we've deployed the clinic microservice, we need to configure the management URI that is used by the HTTP client object. Remember that I initially used the localhost and port from the launch settings json file located in the management project. To do this, we have to use environment variables. So, I'm going to modify the workflow to include the management uri environment variable. However, before I do that, I also want to fix the typo that we have here in the ConsultationController class. And let's fix this, because this is replacing the route that we have here in this attribute. And now, the route is api/consultation/start as intended. Perfect. That said, let's open up the workflow, and let's change the branch name. And here in this part, wpm-clinic, let's add an additional environment variable, which is MangementUri, and the value is http, and the name of the container app that contains the management microservice. In other words, wpm-management. Azure…
Contents
-
-
-
-
-
-
-
(Locked)
Creating the Clinic microservice2m 44s
-
(Locked)
Adding the ClinicDbContext class3m 44s
-
(Locked)
Implementing the ManagementService class5m 41s
-
(Locked)
Implementing the ClinicApplicationService class6m 35s
-
(Locked)
Adding resilience traits to the microservice using Polly3m 20s
-
(Locked)
Creating the Container App for the Clinic microservice1m 2s
-
(Locked)
Creating the Dockerfile and modifying the workflow3m 17s
-
(Locked)
Adding environment variables to the Clinic microservice4m 41s
-
(Locked)
Challenge: Implementing a new endpoint and memory cache1m 30s
-
(Locked)
Solution: Implement a new endpoint and memory cache2m 41s
-
(Locked)
-