Difference between revisions of "Provider.tf"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
[[AWS]] example: | [[AWS]] example: | ||
[[provider]] "aws" { | [[provider]] "aws" { | ||
| − | region = "us-west-2" | + | [[region]] = "us-west-2" |
[[profile]] = "your-profile-name" | [[profile]] = "your-profile-name" | ||
} | } | ||
| Line 14: | Line 14: | ||
[[Google Cloud]] example: | [[Google Cloud]] example: | ||
provider "google" { | provider "google" { | ||
| − | + | region = "[[us-central1]]" | |
| − | + | project = "your-project-name" | |
} | } | ||
Revision as of 17:05, 21 October 2021
skip final snapshot = true
AWS example:
provider "aws" { region = "us-west-2" profile = "your-profile-name" }
Google Cloud example:
provider "google" {
region = "us-central1"
project = "your-project-name"
}
Related terms
See also
- Terraform configuration files, Terraform state files:
.tf,.tfvars,main.tf, outputs.tf,variables.tf,.terraform.d/,terraform init,providers.tf,.terraform/,terraform.tfstate,.terraform.lock.hcl,terraform.tfstate.d, override.tf, versions.tf - Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint, Operators, Expressions:for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising:
