Types are value storage and access mechanism for resource, data source, or provider schema data. Every attribute and block has an associated type, which describes the kind of data. These types fully support Terraform's type system concepts that cannot be represented in Go built-in types, such as *string
. Framework types can be extended by implementing custom types in provider code or shared libraries to provide specific use case functionality.
The framework type system supports the following types:
Types that contain a single data value, such as a boolean, number, or string. These are directly associated with their primitive attribute type.
Type Use Case Bool Boolean true or false Float32 32-bit floating point number Float64 64-bit floating point number Int32 32-bit integer number Int64 64-bit integer number Number Arbitrary precision (generally over 64-bit, up to 512-bit) number String Collection of UTF-8 encoded characters Collection TypesTypes that contain multiple values of a single element type, such as a list, map, or set.
These types are associated with:
Type that defines a mapping of explicit attribute names to value types.
This type is associated with:
Type that defines an ordered collection of elements where each element has it's own type.
Note
This type intentionally includes less functionality than other types in the type system as it has limited real world application and therefore is not exposed to provider developers except when working with dynamic values.
Type Use Case Tuple Ordered collection of multiple element types Dynamic TypeContainer type that can contain any underlying value type, determined by Terraform or the provider at runtime.
Type Use Case Dynamic Any value type of data, determined at runtime.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4