Skip main navigation

Environment Configuration


In the last step, we discussed Infrastructure As Code with Terraform. In this step, we explore environment configuration.

Configuration As Code

Configuration as code, along with Infrastructure as Code, can help you make the management and configuration of your environments automated and consistent.

Configuration as code scripts and environment definitions, when used with tools for managing system configuration, are usually idempotent or can be run multiple times because the scripts or definitions will look for the state of services and install and configure if not running.

Idempotence is the property that a deployment command always sets the target environment into the same configuration, regardless of the environment’s starting state. Idempotency is achieved by either automatically configuring an existing target or by discarding the existing target and re-creating a fresh environment.

The following table lists the major differences between manual configuration and configuration as code

The left column lists Manual Configuration options, and the right column lists Configuration as code, all as listed in the video

In the final step for this activity, we will learn about database as code. Click on Mark as complete to Step off.

This article is from the free online

Microsoft Future Ready: Fundamentals of DevOps and Azure Pipeline

Created by
FutureLearn - Learning For Life

Reach your personal and professional goals

Unlock access to hundreds of expert online courses and degrees from top universities and educators to gain accredited qualifications and professional CV-building certificates.

Join over 18 million learners to launch, switch or build upon your career, all at your own pace, across a wide range of topic areas.

Start Learning now