02576988c1
These are intended to make it easier to work with arbitrary data
structures whose shape might not be known statically, such as the result
of jsondecode(...) or yamldecode(...) of data from a separate system.
For example, in an object value which has attributes that may or may not
be set we can concisely provide a fallback value to use when the attribute
isn't set:
try(local.example.foo, "fallback-foo")
Using a "try to evaluate" model rather than explicit testing fits better
with the usual programming model of the Terraform language where values
are normally automatically converted to the necessary type where possible:
the given expression is subject to all of the same normal type conversions,
which avoids inadvertently creating a more restrictive evaluation model
as might happen if this were handled using checks like a hypothetical
isobject(...) function, etc.
|
||
|---|---|---|
| .. | ||
| backend-types.erb | ||
| commands-providers.erb | ||
| commands-state.erb | ||
| commands-workspace.erb | ||
| docs.erb | ||
| downloads.erb | ||
| functions.erb | ||
| guides.erb | ||
| intro.erb | ||
| registry.erb | ||
| terraform.erb | ||