Task 3.7: Apply formatting and style adjustments to a configuration

• Aterraform fmt -diff

  Incorrect

  -diff shows the formatting changes but still rewrites the files and exits successfully.

• Bterraform validate -json

  Incorrect

  validate checks syntax and consistency, not formatting.

• Cterraform fmt -list=false

  Incorrect

  That only stops fmt from listing the files it changes.

• Dterraform fmt -check

  Correct

  -check exits with a non-zero status when input is not formatted and implies -write=false, so files are not modified.

fmt -check is the CI form of fmt: report and fail, never write.

• ARewrites them in canonical format and lists the files it changed

  Correct

  fmt overwrites files to match the canonical format and lists the files with inconsistencies, unless -list=false or -write=false is set.

• BPrints the problems it finds and leaves the files as they are

  Incorrect

  By default fmt writes its changes; it does not only report them.

• CFails the command until the files are fixed by hand

  Incorrect

  fmt fixes formatting itself.

• DFormats the files in memory for the next plan only

  Incorrect

  fmt writes the changes to the files.

fmt fixes files in place by default.

• A-list=false

  Incorrect

  That hides the list of changed files.

• B-write=true

  Incorrect

  That is the default, which rewrites files without showing the changes.

• C-diff

  Correct

  -diff displays the diffs of formatting changes.

• D-no-color

  Incorrect

  That removes color from output.

-diff shows what fmt changes.

• ANothing; fmt rules are frozen across versions

  Incorrect

  New formatting rules can be added in new versions.

• BRun terraform validate -fmt to convert them to the new version's style

  Incorrect

  There is no such option.

• CDelete the .terraform directory so fmt uses the new rules

  Incorrect

  fmt rules are built into the binary, not cached in .terraform.

• DRun terraform fmt on them, as the canonical format can change slightly

  Correct

  The canonical format may change in minor ways between versions, so the docs recommend running fmt after upgrading.

Formatting rules travel with the Terraform binary; re-run fmt after an upgrade.

• AIndent with one tab character per nesting level

  Incorrect

  The convention is two spaces, not tabs.

• BIndent two spaces for each nesting level

  Correct

  The style guide asks for two-space indentation per nesting level, which fmt applies.

• CAlign the equals signs of consecutive single-line arguments

  Correct

  Consecutive single-line arguments at the same level have aligned equals signs.

• DPut every argument on its own file

  Incorrect

  Files group related blocks; there is no one-argument-per-file rule.

• EWrite all block types in uppercase

  Incorrect

  Block types are lowercase keywords.

Two spaces and aligned equals signs: the two layout rules readers notice most.

• AUse terraform fmt -list=network.tf

  Incorrect

  -list is a true or false switch for listing changed files, not a file selector.

• BPass the file as the target: terraform fmt network.tf

  Correct

  fmt accepts targets, such as a file or directory, instead of scanning the current directory.

• CUse terraform fmt -target=network.tf

  Incorrect

  -target belongs to plan and apply, not fmt.

• DRename every other file in the directory temporarily, then rename them back

  Incorrect

  Targets make that unnecessary.

fmt formats the current directory by default, or exactly the targets you give it.