Remove more references to Atlas

This commit is contained in:
Seth Vargo 2017-04-07 11:36:49 -04:00
parent 2ff3d47f30
commit 91d5e75afa
1 changed files with 16 additions and 11 deletions

View File

@ -6,23 +6,23 @@ description: |-
Accesses state meta data from a remote backend.
---
# remote\_state
# remote_state
Retrieves state meta data from a remote backend
## Example Usage
```
```hcl
data "terraform_remote_state" "vpc" {
backend = "atlas"
config {
name = "hashicorp/vpc-prod"
}
backend = "atlas"
config {
name = "hashicorp/vpc-prod"
}
}
resource "aws_instance" "foo" {
# ...
subnet_id = "${data.terraform_remote_state.vpc.subnet_id}"
# ...
subnet_id = "${data.terraform_remote_state.vpc.subnet_id}"
}
```
@ -47,11 +47,14 @@ on the `terraform_remote_state` resource.
## Root Outputs Only
Only the root level outputs from the remote state are accessible. Outputs from modules within the state cannot be accessed. If you want a module output to be accessible via a remote state, you must thread the output through to a root output.
Only the root level outputs from the remote state are accessible. Outputs from
modules within the state cannot be accessed. If you want a module output to be
accessible via a remote state, you must thread the output through to a root
output.
An example is shown below:
```
```hcl
module "app" {
source = "..."
}
@ -61,4 +64,6 @@ output "app_value" {
}
```
In this example, the output `value` from the "app" module is available as "app_value". If this root level output hadn't been created, then a remote state resource wouldn't be able to access the `value` output on the module.
In this example, the output `value` from the "app" module is available as
"app_value". If this root level output hadn't been created, then a remote state
resource wouldn't be able to access the `value` output on the module.