ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/website/docs/language/resources/index.html.md

35 lines
1.5 KiB
Markdown
Raw Normal View History

website: Add new "glue"/overview pages for CLI and language docs The new nav structure demanded a few new pages that give context about a feature or workflow. In a few cases, they take text from an existing page. Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Judith Malnick <judith.patudith@gmail.com>
2020-10-27 02:15:36 +01:00
---
layout: "language"
page_title: "Resources Overview - Configuration Language"
---
# Resources
> **Hands-on:** Try the [Terraform: Get Started](https://learn.hashicorp.com/collections/terraform/aws-get-started?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) collection on HashiCorp Learn.
_Resources_ are the most important element in the Terraform language.
Each resource block describes one or more infrastructure objects, such
as virtual networks, compute instances, or higher-level components such
as DNS records.
website: Language: Update links to moved pages
2021-01-15 23:13:53 +01:00
- [Resource Blocks](/docs/language/resources/syntax.html) documents
website: Break up Resources page into smaller chunks - Resource behavior gets its own page. - Meta-arguments all get their own pages. - Stuff about resource syntax itself gets a page. In the process of breaking the meta-arguments out into their own pages, I revised them (with the exception of `provider`) so that they apply to both resources and modules. Like with Expressions, this commit repurposes the old resources.html URL as a landing page for old links.
2020-11-13 03:06:32 +01:00
the syntax for declaring resources.
website: Language: Update links to moved pages
2021-01-15 23:13:53 +01:00
- [Resource Behavior](/docs/language/resources/behavior.html) explains in
website: Break up Resources page into smaller chunks - Resource behavior gets its own page. - Meta-arguments all get their own pages. - Stuff about resource syntax itself gets a page. In the process of breaking the meta-arguments out into their own pages, I revised them (with the exception of `provider`) so that they apply to both resources and modules. Like with Expressions, this commit repurposes the old resources.html URL as a landing page for old links.
2020-11-13 03:06:32 +01:00
more detail how Terraform handles resource declarations when applying a
configuration.
- The Meta-Arguments section documents special arguments that can be used with
every resource type, including
website: Language: Update links to moved pages
2021-01-15 23:13:53 +01:00
[`depends_on`](/docs/language/meta-arguments/depends_on.html),
[`count`](/docs/language/meta-arguments/count.html),
[`for_each`](/docs/language/meta-arguments/for_each.html),
[`provider`](/docs/language/meta-arguments/resource-provider.html),
and [`lifecycle`](/docs/language/meta-arguments/lifecycle.html).
website: Break up Resources page into smaller chunks - Resource behavior gets its own page. - Meta-arguments all get their own pages. - Stuff about resource syntax itself gets a page. In the process of breaking the meta-arguments out into their own pages, I revised them (with the exception of `provider`) so that they apply to both resources and modules. Like with Expressions, this commit repurposes the old resources.html URL as a landing page for old links.
2020-11-13 03:06:32 +01:00
website: Language: Update links to moved pages
2021-01-15 23:13:53 +01:00
- [Provisioners](/docs/language/resources/provisioners/index.html)
website: Add new "glue"/overview pages for CLI and language docs The new nav structure demanded a few new pages that give context about a feature or workflow. In a few cases, they take text from an existing page. Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Judith Malnick <judith.patudith@gmail.com>
2020-10-27 02:15:36 +01:00
documents configuring post-creation actions for a resource using the
`provisioner` and `connection` blocks. Since provisioners are non-declarative
and potentially unpredictable, we strongly recommend that you treat them as a
last resort.