Managing the configuration settings of an application is an increasingly important aspect of modern software development. These configurations used to be stored with their associated application code repositories and any changes required a new version of the code to be deployed, even if a single configuration needed to be changed.

As teams nowadays work on bigger and more complex projects, the need for better configuration management arose. Implementing Configuration as Code can help software development teams continuously deliver higher quality products, fast. Using Configuration as Code implies that the configurations are stored in their own repository and managed in a different process from the primary codebase.

In this tutorial, we will explore what Configuration as Code means, how to use it, and the benefits of storing and managing it separately from the application codebase.