Book Image

Learning DevOps - Second Edition

By : Mikael Krief
Book Image

Learning DevOps - Second Edition

By: Mikael Krief

Overview of this book

In the implementation of DevOps processes, the choice of tools is crucial to the sustainability of projects and collaboration between developers and ops. This book presents the different patterns and tools for provisioning and configuring an infrastructure in the cloud, covering mostly open source tools with a large community contribution, such as Terraform, Ansible, and Packer, which are assets for automation. This DevOps book will show you how to containerize your applications with Docker and Kubernetes and walk you through the construction of DevOps pipelines in Jenkins as well as Azure pipelines before covering the tools and importance of testing. You'll find a complete chapter on DevOps practices and tooling for open source projects before getting to grips with security integration in DevOps using Inspec, Hashicorp Vault, and Azure Secure DevOps kit. You'll also learn about the reduction of downtime with blue-green deployment and feature flags techniques before finally covering common DevOps best practices for all your projects. By the end of this book, you'll have built a solid foundation in DevOps and developed the skills necessary to enhance a traditional software delivery process using modern software delivery tools and techniques.
Table of Contents (25 chapters)
1
Section 1: DevOps and Infrastructure as Code
7
Section 2: DevOps CI/CD Pipeline
11
Section 3: Containerized Microservices with Docker and Kubernetes
14
Section 4: Testing Your Application
18
Section 5: Taking DevOps Further/More on DevOps

Chapter 2: Provisioning Cloud Infrastructure with Terraform

  1. The language used by Terraform is HashiCorp Configuration Language (HCL).
  2. Terraform's role is as an Infrastructure as Code tool.
  3. No. Terraform is not a scripting tool.
  4. The command that allows you to display the installed version is terraform version.
  5. The name of the Azure object that connects Terraform to Azure is the Azure Service Principal.
  6. The three main commands of Terraform are terraform init, terraform plan, and terraform apply.
  7. The Terraform command that allows us to destroy resources is terraform destroy.
  8. We add the --auto-approve option to the terraform apply command.
  9. The purpose of the Terraform state file is to keep the resources and their properties throughout the execution of Terraform.
  10. No, it is not a good practice to store a Terraform state file locally; it must be stored in a protected remote backend.