Chapter 2. Input Variables
Understanding input variables is a natural starting point to writing high-quality, highly scalable TF projects. Typically, these variables are introduced to provide abstraction to TF projects, enabling reusability of configuration and easy updates to modifiable resource attributes. However, for projects that are intended to be preserved, they should be introduced early in the project development.
In this chapter, you’ll review the various ways variability may be introduced, focusing on the input variable component itself. You’ll also gain exposure to the other governance capabilities that input variables provide, such as type constraints and validation{} blocks. By the end of this chapter, you’ll understand how to create high-quality input variables that optimize the balance between expressiveness and control.
Variability of TF Configuration
As an IaC platform, TF is primarily concerned with taking encoded infrastructure configuration information and applying it in an idempotent fashion such that the result is the same no matter how many times you execute it against the same configuration. It evaluates the contents of the .tf and .tfvars files (and the provider code it depends on) to construct the execution plan. As presented in Chapter 1, this execution plan is an immutable script and cannot be modified once it’s constructed. However, as was also covered, there are usually multiple ways to construct the HCL configuration that you write to arrive at ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access