Difference between revisions of "Terraform init -backend-config"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
| − | * <code>[[terraform init -backend-config | + | * <code>[[terraform init]] -backend-config=bucket=your_bucket_name -backend-config=key=your-key-name/project/***/state.tfstate -backend-config=region=XXXXX -backend-config=access_key=XXXX -backend-config=secret_key=XXXX</code> |
-backend-config=path Configuration to be merged with what is in the | -backend-config=path Configuration to be merged with what is in the | ||
| Line 11: | Line 11: | ||
times. The backend type must be in the configuration | times. The backend type must be in the configuration | ||
itself. | itself. | ||
| + | |||
| + | == Related == | ||
| + | * [[Terraform backends]] | ||
== See also == | == See also == | ||
Latest revision as of 19:04, 26 September 2022
terraform init -backend-config=bucket=your_bucket_name -backend-config=key=your-key-name/project/***/state.tfstate -backend-config=region=XXXXX -backend-config=access_key=XXXX -backend-config=secret_key=XXXX
-backend-config=path Configuration to be merged with what is in the
configuration file's 'backend' block. This can be
either a path to an HCL file with key/value
assignments (same format as terraform.tfvars) or a
'key=value' format, and can be specified multiple
times. The backend type must be in the configuration
itself.
Related[edit]
See also[edit]
Advertising:
