Each provider may offer data sources
alongside its set of resource
types.
Data Sources - Configuration Language | Terraform | HashiCorp Developer - 0 views
-
-
When distinguishing from data resources, the primary kind of resource (as declared by a resource block) is known as a managed resource.
-
Each data resource is associated with a single data source, which determines the kind of object (or objects) it reads and what query constraint arguments are available.
- ...4 more annotations...
Providers - Configuration Language | Terraform | HashiCorp Developer - 0 views
-
Terraform relies on plugins called providers to interact with cloud providers, SaaS providers, and other APIs.
-
Terraform configurations must declare which providers they require so that Terraform can install and use them.
-
Each provider adds a set of resource types and/or data sources that Terraform can manage.
- ...6 more annotations...
Syntax - Configuration Language | Terraform | HashiCorp Developer - 0 views
-
the native syntax of the Terraform language, which is a rich language designed to be relatively easy for humans to read and write.
-
Terraform's configuration language is based on a more general language called HCL, and HCL's documentation usually uses the word "attribute" instead of "argument."
-
A particular block type may have any number of required labels, or it may require none
- ...34 more annotations...
The for_each Meta-Argument - Configuration Language | Terraform | HashiCorp Developer - 0 views
-
A given resource or module block cannot use both count and for_each
-
The for_each meta-argument accepts a map or a set of strings, and creates an instance for each item in that map or set
-
each.key — The map key (or set member) corresponding to this instance.
- ...10 more annotations...
1 - 5 of 5
Showing 20▼ items per page