terraform/lang
Martin Atkins 2f8f7d6f4d lang/funcs: Type conversion functions
It's not normally necessary to make explicit type conversions in Terraform
because the language implicitly converts as necessary, but explicit
conversions are useful in a few specialized cases:

- When defining output values for a reusable module, it may be desirable
  to force a "cleaner" output type than would naturally arise from a
  computation, such as forcing a string containing digits into a number.
- Our 0.12upgrade mechanism will use some of these to replace use of the
  undocumented, hidden type conversion functions in HIL, and force
  particular type interpretations in some tricky cases.
- We've found that type conversion functions can be useful as _temporary_
  workarounds for bugs in Terraform and in providers where implicit type
  conversion isn't working correctly or a type constraint isn't specified
  precisely enough for the automatic conversion behavior.

These all follow the same convention of being named "to" followed by a
short type name. Since we've had a long-standing convention of running all
the words together in lowercase in function names, we stick to that here
even though some of these names are quite strange, because these should
be rarely-used functions anyway.
2019-01-17 10:01:47 -08:00
..
funcs lang/funcs: Type conversion functions 2019-01-17 10:01:47 -08:00
data.go core: Static-validate resource references against schemas 2018-11-26 08:25:03 -08:00
data_test.go core: Static-validate resource references against schemas 2018-11-26 08:25:03 -08:00
doc.go
eval.go core: Validate depends_on and ignore_changes traversals 2018-12-17 09:02:25 -08:00
eval_test.go move "configschema" from "config" to "configs" 2018-10-16 18:50:29 -07:00
functions.go lang/funcs: Type conversion functions 2019-01-17 10:01:47 -08:00
references.go move "configschema" from "config" to "configs" 2018-10-16 18:50:29 -07:00
scope.go terraform: ugly huge change to weave in new HCL2-oriented types 2018-10-16 18:46:46 -07:00