opentf

mirror of https://github.com/opentffoundation/opentf.git synced 2026-04-19 12:02:06 -04:00

Files

Martin Atkins f3a2165587 website: Use "Input Variable" as full term for var.foo

We've historically been somewhat inconsistent in how we refer to the
type of object defined by "variable" blocks in configuration. Parts of
our documentation refer to them as "input variables" or just "variables",
while our implementation refers to them as "user variables".

Since Terraform Registry is now also referring to these as "Inputs", here
we standardize on "Input Variable" as the fully-qualified name for this
concept, with "variable" being a shorthand for this where context is
obvious. Outside of this context, anything that can be referred to in
an interpolation expression is generically known as a "variable", with
Input Variables being just one kind, specified by the "var." prefix.

While this terminology shift is not critical yet, it will become more
important as we start to document the new version of the configuration
language so we can use the generic meaning of "variable" there.

2017-11-09 11:08:09 -08:00

data-sources.html.md

website: new filesystem layout for core/provider split

2017-06-13 11:25:32 -07:00

environment-variables.html.md

command: Allow TF_DATA_DIR env var to override data directory

2017-11-01 16:55:23 -07:00

index.html.md

website: new filesystem layout for core/provider split

2017-06-13 11:25:32 -07:00

interpolation.html.md

website: correction of chunklist interpolation function example