Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “Troubleshooting errors may depend on the cloud provider, so it’s a good idea to use PACKER_LOG=1 as you develop these templates. ”

A block of code is set as follows:

post-processor "compress" {
  output = "{{.BuildName}}.gz"
  compression_level = 7
}

Any command-line input or output is written as follows:

$ curl -X POST --data "{\"token\": \"$GITHUB_TOKEN\"}" \
   http://yourvault:8200/v1/auth/github/login \
   | jq –r .auth.client_token

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “Remember you need administrative rights to your repo to access the Actions menu.”

Tips or important notes

Appear like this.