IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-30 10:47:14 -06:00
Code Issues Packages Projects Releases Wiki Activity
39ef97beff
opentofu/website/docs/internals/resource-addressing.html.markdown
Martin Atkins 04f3766fd9 website: Indicate v0.12-only content 
We have released the v0.12-oriented content to the website early in order
to support the beta process, but in some places we neglected to explicitly
mark features or content as being v0.12-only.

Here we add explicit markers to the main cases we've seen where readers
have reported confusion, along with some other tweaks in similar vein.
2019-03-18 12:42:21 -07:00

1.8 KiB
Raw Blame History

layout page_title sidebar_current description
docs Internals: Resource Address docs-internals-resource-addressing Resource addressing is used to target specific resources in a larger infrastructure.

Resource Addressing

A Resource Address is a string that references a specific resource in a larger infrastructure. An address is made up of two parts:

[module path][resource spec]

Module path:

A module path addresses a module within the tree of modules. It takes the form:

module.A.module.B.module.C...

Multiple modules in a path indicate nesting. If a module path is specified without a resource spec, the address applies to every resource within the module. If the module path is omitted, this addresses the root module.

Resource spec:

A resource spec addresses a specific resource in the config. It takes the form:

resource_type.resource_name[N]
  • resource_type - Type of the resource being addressed.
  • resource_name - User-defined name of the resource.
  • [N] - where N is a 0-based index into a resource with multiple instances specified by the count meta-parameter. Omitting an index when addressing a resource where count > 1 means that the address references all instances.

-> In Terraform v0.12 and later, a resource spec without a module path prefix matches only resources in the root module. In earlier versions, a resource spec without a module path prefix will match resources with the same type and name in any descendent module.

Examples

Given a Terraform config that includes:

resource "aws_instance" "web" {
  # ...
  count = 4
}

An address like this:

aws_instance.web[3]

Refers to only the last instance in the config, and an address like this:

aws_instance.web

Refers to all four "web" instances.