DevOps

7.

Infrastructure as Code

7.1.

7.1.1.

Declarative vs Imperative

7.1.1.1.

Declarative Configuration

7.1.1.2.

Imperative Scripting

7.1.1.3.

Hybrid Approaches

7.1.2.

7.1.2.1.

Consistent State Management

7.1.2.2.

Safe Re-execution

7.1.2.3.

State Drift Prevention

7.1.3.

Version Control for Infrastructure

7.1.3.1.

Infrastructure Versioning

7.1.3.2.

Change Tracking

7.1.3.3.

Rollback Capabilities

7.2.

Configuration Management

7.2.1.

Configuration Management Concepts

7.2.1.1.

Desired State Configuration

7.2.1.2.

Configuration Drift

7.2.1.3.

Compliance Enforcement

7.2.2.

7.2.2.1.

Playbooks and Tasks

7.2.2.2.

Inventory Management

7.2.2.3.

Roles and Collections

7.2.2.4.

7.2.3.

7.2.3.1.

Manifests and Classes

7.2.3.2.

7.2.3.3.

Puppet Server Architecture

7.2.3.4.

Hiera Data Management

7.2.4.

7.2.4.1.

Cookbooks and Recipes

7.2.4.2.

Chef Server and Nodes

7.2.4.3.

Data Bags and Environments

7.2.4.4.

7.2.5.

7.2.5.1.

States and Pillars

7.2.5.2.

Salt Master and Minions

7.2.5.3.

Event-Driven Automation

7.3.

Infrastructure Provisioning

7.3.1.

Cloud Infrastructure Provisioning

7.3.1.1.

Resource Lifecycle Management

7.3.1.2.

Multi-Cloud Strategies

7.3.1.3.

Cost Optimization

7.3.2.

7.3.2.1.

HCL Configuration Language

7.3.2.2.

Providers and Resources

7.3.2.3.

State Management

7.3.2.4.

Modules and Workspaces

7.3.3.

Cloud-Specific Tools

7.3.3.1.

AWS CloudFormation

7.3.3.2.

Azure Resource Manager

7.3.3.3.

Google Cloud Deployment Manager

7.3.4.

Hybrid and Multi-Cloud

7.3.4.1.

Cross-Cloud Provisioning

7.3.4.2.

Vendor Lock-in Avoidance

7.3.4.3.

Consistency Across Platforms

Previous

6. Continuous Delivery and Deployment

Go to top

Next

8. Containerization