Projects grow - sometimes faster than we expect. We know that manual work takes more time. I'll show how I automated the service deployment process after issues caused by adding the test environment. Our team has developed a service for processing messages from Kafka. It is a console application that subscribes to topics, and when messages appear against each of them, a processing algorithm is executed. During the first iterations, the deployment was quite simple: we publish the service locally, copy build files to the server, create a docker image, and start the service in a container. We lived like this until the test team joined us and deployed in a testing environment. The configuration file in this environment was different. Therefore, we faced another chore - fixing the configuration file manually. At this stage, the human factor intervened; sometimes, we forgot to edit the file, which led to errors and loss of time. appsettings.json When we got tired of it, we decided to call DevOps to help. However, it still took time. Therefore I came up with an idea and implemented a quick solution for handling multiple environments. Here are the details: Initial Conditions Our service is a console application, and we didn't have out-of-the-box solutions as provided in the ASP.NET Core web application. The application is launched from the docker container. Setup Console App Well, let's see how to use multi-configuration in a console application. First, let's create files for our environments Testing and development: There is no default nesting in console applications. Therefore, open the and add: .csproj project file Always appsettings.json Always < > ItemGroup < = > Content Include "appsettings.json" < > CopyToOutputDirectory </ > CopyToOutputDirectory </ > Content < = > Content Include "appsettings.Dev.json;appsettings.Testing.json;" < > DependentUpon </ > DependentUpon < > CopyToOutputDirectory </ > CopyToOutputDirectory </ > Content </ > ItemGroup It looks much better, right? Afterward, I attach files with the name of the development environment that appeared in the file: appsettings.json The contains parts of the config that change relative to the environment. For example, we change the name of the topics for Kafka in the load testing loop: appsettings.{Environment}.json { : { : , : , : }
} "Kafka" "EventMainTopicTitle" "Test_EventMain" "EventDelayTopicTitle" "Test_EventDelay" "EventRejectTopicTitle" "Test_EventReject" Now, we just need to select the suitable file during the start of the service. To do this, let's make changes to the program class: appsettings.json { environmentVariableName = ; environmentName =
        Environment.GetEnvironmentVariable (environmentVariable name); services = ServiceCollection ();
    _configuration = ConfigurationBuilder ()
        .SetBasePath (Directory.GetParent (AppContext.BaseDirectory) .FullName)
        .AddJsonFile ( )
        .AddJsonFile ($ )
        .AddEnvironmentVariables ()
        .Build();
    services.AddSingleton (_configuration);
    services.AddSingleton <KafkaHandler> (); services.BuildServiceProvider ();
} /// <summary> Service configuration /// /// </summary> IServiceProvider ( ) private static ConfigureServices const string "ASPNETCORE_ENVIRONMENT" var var new new "appsettings.json" "appsettings. {EnvironmentName} .json" return Setup Docker Container Now everything is ready to start the service in a docker container. First, you need to specify the environment variables for the container. There are several ways to do this: command line text file docker compose I settled on specifying the index in the string. Here's an example script to create an image and run a container: # Create image # build docker. -t consoleapp # Run container on Dev # docker run -d --env ASPNETCORE_ENVIRONMENT = Dev --name app consoleapp Conclusion There are more elegant solutions for pipeline deployment. However, this solution can save time and human resources which are very critical in the early stages of building applications. Thanks for your attention and happy coding! GitHub project: https://github.com/AnnaVosh/AutomaticallySetupConfigFile

Different

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

How to Handle Configuration for Multiple Environments in Console App Service?

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

5 Performance Tips For .Net Developers

6 Best C# Programming Books Ranked by Review Score

7 C# Tips for Beginners in Programming Language

A Beginner's Guide Formatting Strings as Base64 in CSharp

A Critical Detail about Kafka Partitioners

5 Performance Tips For .Net Developers

6 Best C# Programming Books Ranked by Review Score

7 C# Tips for Beginners in Programming Language

A Beginner's Guide Formatting Strings as Base64 in CSharp

A Critical Detail about Kafka Partitioners

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps