Difference between revisions of "Terraform data source: terraform remote state"
Jump to navigation
Jump to search
(→Errors) |
|||
Line 56: | Line 56: | ||
* <code>[[Error: AccessDenied: Access Denied]]</code> | * <code>[[Error: AccessDenied: Access Denied]]</code> | ||
* <code>[[Error: Unable to find remote state]]</code> | * <code>[[Error: Unable to find remote state]]</code> | ||
+ | |||
+ | == Activities == | ||
+ | * [[Explain the benefits of state]] | ||
== Related == | == Related == |
Revision as of 16:57, 19 April 2023
terraform_remote_state
Controlled Remote State Access feature in Terraform Cloud and Terraform Enterprise, users now have a new way to establish granular controls for state accessibility.
Contents
Example Usage (remote Backend)
data "terraform_remote_state" "vpc" { backend = "remote" config = { organization = "hashicorp" workspaces = { name = "vpc-prod" } } }
# Terraform >= 0.12 resource "aws_instance" "foo" { # ... subnet_id = data.terraform_remote_state.vpc.outputs.subnet_id } # Terraform <= 0.11 resource "aws_instance" "foo" { # ... subnet_id = "${data.terraform_remote_state.vpc.subnet_id}" }
Example Usage (local Backend)
data "terraform_remote_state" "vpc" { backend = "local" config = { path = "..." } } # Terraform >= 0.12 resource "aws_instance" "foo" { # ... subnet_id = data.terraform_remote_state.vpc.outputs.subnet_id } # Terraform <= 0.11 resource "aws_instance" "foo" { # ... subnet_id = "${data.terraform_remote_state.vpc.subnet_id}" }
Errors
Activities
Related
See also
terraform state [ list ]
- Terraform state:
terraform state
[list
|mv
|show
|pull
|push
|rm
|replace-provider
],terraform state show module.alb.aws lb.this
- Terraform data sources:
aws_vpc
,template_file
,aws_subnet_ids
,terraform remote state
,aws_eks_cluster
,aws_ami, aws_availability_zones, aws_partition, archive_file
- Terraform state:
terraform [ state | replace-provider | mv ]
,backend.tf
, Remote state backends to manage Terraform state, State locking,terraform force-unlock
Advertising: