Configuration management

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

The practice of maintaining systems in a defined configuration state across their lifecycle.

Configuration management maintains servers and resources in a desired state by applying defined packages and attributes across systems. section 1.5.3

Apply it to operational infrastructure by:

• Reviewing or updating approved package versions across large server fleets with one command. section 1.5.3
• Separating monolithic automation into independent modules, then extracting dependent configuration through dependency injection. section 10.2.3
• Rolling forward a reverted server state, such as uninstalling version 3.0.0 and reinstalling version 2.0.0. section 11.1.1

Package-state correction

When a server has package version 3.0.0 but requires 2.0.0, the configuration manager removes the newer version and installs the older one, producing a new working state rather than restoring the exact prior state. section 11.1.1

Figure 10.11 The workflow for refactoring an IaC monolith starts by identifying high-level resources with no dependencies.

Use the workflow figure to trace refactoring from independent infrastructure components toward configuration with dependencies. section 10.2.3

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

How deep it goes

Defines fleet configuration, gives refactoring and recovery procedures, and defers detailed guidance for individual tools.

Examples

Uses 10,000-server package updates, modular refactoring, and package-version reversion as operational examples.

What it assumes

Assumes familiarity with servers, resources, packages, and infrastructure automation while defining configuration management itself.

What you can do after

Operate configuration tools to enforce fleet-wide package states, refactor automation, and recover servers through forward changes.

How it connects

Connects configuration management with infrastructure as code, provisioning, dependency injection, infrastructure testing, and security.

liveBookmanning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  100 SQL Server Mistakes and How to Avoid ThemConfiguration management is the practice of maintaining systems in a known, consistent, and compliant state throughout their lifecycle.
• 

  liveBookmanning.com
  Acing the CCNA Exam: Volume 2 Advanced Networking and SecurityConfiguration management is the systematic process of defining, applying, tracking, and enforcing the configurations of devices or other infrastructure.

Compare how 3 books explain configuration management →

Related concepts

• immutable collectioncontrasts with · An immutable collection is a collection whose membership and contents cannot be changed after creation.
• driftaddresses · Drift is a change over time in a system’s behavior, state, data, or configuration relative to a reference or expected baseline.
• environment variableuses · An environment variable is a named value supplied through an operating-system or process environment and made available to programs for runtime configuration or information.
• SQL Server instanceconfigures · A SQL Server instance is an independently configured and running installation of SQL Server that hosts databases, provides database services, and accepts connections.
• feature flaguses · A feature flag is a configuration control that conditionally enables, disables, or selects a software feature or behavior.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.