Book Image

Go for DevOps

By : John Doak, David Justice
5 (1)
Book Image

Go for DevOps

5 (1)
By: John Doak, David Justice

Overview of this book

Go is the go-to language for DevOps libraries and services, and without it, achieving fast and safe automation is a challenge. With the help of Go for DevOps, you'll learn how to deliver services with ease and safety, becoming a better DevOps engineer in the process. Some of the key things this book will teach you are how to write Go software to automate configuration management, update remote machines, author custom automation in GitHub Actions, and interact with Kubernetes. As you advance through the chapters, you'll explore how to automate the cloud using software development kits (SDKs), extend HashiCorp's Terraform and Packer using Go, develop your own DevOps services with gRPC and REST, design system agents, and build robust workflow systems. By the end of this Go for DevOps book, you'll understand how to apply development principles to automate operations and provide operational insights using Go, which will allow you to react quickly to resolve system failures before your customers realize something has gone wrong.
Table of Contents (22 chapters)
1
Section 1: Getting Up and Running with Go
10
Section 2: Instrumenting, Observing, and Responding
14
Section 3: Cloud ready Go

Understanding Go's Context type

Go provides a package called context that is useful for two purposes, as outlined here:

  • Canceling a chain of function calls after some event (such as a timeout)
  • Passing information through a chain of function calls (such as user information)

A Context object is usually created in either main() or at the point of ingestion of some request (such as an RPC or HyperText Transfer Protocol (HTTP) request). A basic Context object is created from our background Context object, as follows:

import "context" 
func main() { 
     ctx := context.Background()
}

The context package and the Context type is an advanced subject, but I want to introduce it here as you will see it used throughout the Go ecosystem.

Using a Context to signal a timeout

Context is often used to communicate a timer state or to terminate a wait condition—for example, when your program is waiting for a network response.

...