resilien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

depends_on doc updates 

Update depends_on for modules and data sources.
This commit is contained in:
James Bardin 2020-05-28 16:17:01 -04:00
parent 01f91316da
commit 5d64029275
2 changed files with 9 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/docs/configuration/data-sources.html.md
View File

@ -114,18 +114,8 @@ operation, and is re-calculated each time a new plan is created.
Data resources have the same dependency resolution behavior Data resources have the same dependency resolution behavior
[as defined for managed resources](./resources.html#resource-dependencies). [as defined for managed resources](./resources.html#resource-dependencies).
Setting the `depends_on` meta-argument within `data` blocks defers reading of
In particular, the `depends_on` meta-argument is also available within `data` the data source until after all changes to the dependencies have been applied.
blocks, with the same meaning and syntax as in `resource` blocks.
However, due to the data resource behavior of deferring the read until the
apply phase when depending on values that are not yet known, using `depends_on`
with data resources will force the read to _always_ be deferred to the apply
phase, and therefore a configuration that uses `depends_on` with a data
resource can never converge.
Due to this behavior, we do not recommend using `depends_on` with data
resources.
## Multiple Resource Instances ## Multiple Resource Instances

10
website/docs/configuration/modules.html.md
View File

@ -158,9 +158,13 @@ described in more detail in other sections:
If not specified, the child module inherits all of the default (un-aliased) If not specified, the child module inherits all of the default (un-aliased)
provider configurations from the calling module. provider configurations from the calling module.
In addition to the above, the argument names `depends_on` and * `depends_on` - (Optional) Create explicit dependencies between the entire
`lifecycle` are not currently used by Terraform but are reserved for planned module and the listed targets. This will delay the final evaluation of the
future features. module, and any sub-modules, until after the dependencies have been applied.
Modules have the same dependency resolution behavior [as defined for managed resources](./resources.html#resource-dependencies).
In addition to the above, the `lifecycle` argument is not currently used by
Terraform but is reserved for planned future features.
Since modules are a complex feature in their own right, further detail Since modules are a complex feature in their own right, further detail
about how modules can be used, created, and published is included in about how modules can be used, created, and published is included in