596e529602
As of this commit, that layout doesn't exist yet, but I'm isolating the one-line changes to their own commit to try and keep your eyes from glazing over.
1.6 KiB
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| language | Load Order and Semantics - 0.11 Configuration Language | docs-conf-old-load | When invoking any command that loads the Terraform configuration, Terraform loads all configuration files within the directory specified in alphabetical order. |
Load Order and Semantics
-> Note: This page is about Terraform 0.11 and earlier. For Terraform 0.12 and later, see Configuration Language.
When invoking any command that loads the Terraform configuration, Terraform loads all configuration files within the directory specified in alphabetical order.
The files loaded must end in
either .tf or .tf.json to specify the format that is in use.
Otherwise, the files are ignored. Multiple file formats can
be present in the same directory; it is okay to have one Terraform
configuration file be Terraform syntax and another be JSON.
Override files are the exception, as they're loaded after all non-override files, in alphabetical order.
The configuration within the loaded files are appended to each other. This is in contrast to being merged. This means that two resources with the same name are not merged, and will instead cause a validation error. This is in contrast to overrides, which do merge.
The order of variables, resources, etc. defined within the configuration doesn't matter. Terraform configurations are declarative, so references to other resources and variables do not depend on the order they're defined.