set up resource page and reference area #36617
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-ref-rewrite' into docs/resource-block-ref-rewrite merging changes pulled from main rollup branch into local working branch
trujillo-adam
added
the
no-changelog-needed
rkoron007
force-pushed
the
docs/march-sprint-lang-rewrites
branch
3 times, most recently
from
d2adaa0 to
92b1b12
Compare
rkoron007
reviewed
Mar 31, 2025
| @@ -43,7 +43,9 @@ You can use a scoped data source to validate the status of a piece of infrastruc | |||
|
|
|||
| #### Meta-Arguments | |||
|
|
|||
| Scoped data sources support the `depends_on` and `provider` [meta-arguments](/terraform/language/resources/syntax#meta-arguments). Scoped data sources do not support the `count` or`for_each` meta-arguments. | |||
| Meta-arguments are arguments built into Terraform that control how Terraform creates and manages resources. [Meta-arguments](/terraform/language/meta-arguments) for additional information. | |||
There was a problem hiding this comment.
Can you take this change out? This is the page I'm replacing and I don't want you to have a merge conflict!
rkoron007
reviewed
Mar 31, 2025
| @@ -9,7 +9,7 @@ description: >- | |||
| The `terraform state rm` command removes the binding to an existing remote object without first destroying it. The remote object continues | |||
| to exist but is no longer managed by Terraform. | |||
|
|
|||
| Instead of using the `terraform state rm` command, you can use `removed` blocks to remove resources. You can remove more than one resource at a time, and you can review removals as part of your normal plan and apply workflow. [Learn more about using `removed` blocks with resources](/terraform/language/resources/syntax#removing-resources) and [using `removed` blocks with modules](/terraform/language/modules/syntax#removing-modules). | |||
| Instead of using the `terraform state rm` command, you can use `removed` blocks to remove resources. You can remove more than one resource at a time, and you can review removals as part of your normal plan and apply workflow. Refer to the [`removed` block reference](/terraform/language/block/removed) for additional information about removing resources. Refer to [Removing modules](/terraform/language/modules/syntax#removing-modules) for information about removing modules. | |||
There was a problem hiding this comment.
We won't have a removed block reference yet though, right? So the /terraform/language/block/removed link won't work?
rkoron007
reviewed
Mar 31, 2025
| @@ -7,7 +7,7 @@ description: Stacks help you provision and coordinate your infrastructure lifecy | |||
|
|
|||
| A deployment configuration file defines how to deploy your Stack's infrastructure. Each Stack deployment runs in its agent, wholly isolated from other Stack deployments. | |||
|
|
|||
| Every Stack needs a deployment configuration file, `tfdeploy.hcl`, and this page describes all of the blocks you can use within a deployment configuration file. Note that none of the blocks in the deployment configuration file support [meta-arguments](/terraform/language/resources/syntax#meta-arguments). | |||
| Every Stack needs a deployment configuration file, `tfdeploy.hcl`, and this page describes all of the blocks you can use within a deployment configuration file. Note that none of the blocks in the deployment configuration file support [meta-arguments](/terraform/language/meta-arguments). | |||
There was a problem hiding this comment.
There is no /terraform/language/meta-arguments because there is no index page for that directory.
rkoron007
changed the base branch from
docs/march-sprint-lang-rewrites
to
docs/reference-rewrites-phrase-1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements Jira story IPE-1066 and is part of the Terraform information architecture redesign. It several existing page with a new reference page that describes arguments you can use in a
resourceblock. It also factors the resources overview page, which describes the resource creation and management workflow.I will create another PR to implement IPE-1067, which is the companion to 1066. The companion story outlines new usage pages that describe how to create and manage resources in Terraform configuration.