Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy-manage/deploy/_snippets/tpec.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
The {{ecloud}} Terraform provider allows you to provision and manage {{ech}} and {{ece}} deployments as code, and introduce DevOps-driven methodologies to manage and deploy the {{stack}} and solutions.

To get started, see the [{{ecloud}} Terraform provider documentation](https://registry.terraform.io/providers/elastic/ec/latest/docs).
To get started, review the [{{ecloud}} Terraform provider documentation](https://registry.terraform.io/providers/elastic/ec/latest/docs) and [{{ecloud}} Terraform GitHub repository](https://github.com/elastic/terraform-provider-ec) for more guidance.
4 changes: 2 additions & 2 deletions deploy-manage/deploy/elastic-cloud/tools-apis.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,11 +96,11 @@ serverless: unavailable
:::


## Provision deployments with Terraform
## Provision projects and deployments with Terraform
```{applies_to}
deployment:
ess: ga
serverless: unavailable
serverless: ga
Copy link
Contributor

@yetanothertw yetanothertw Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this situation (where we want to signal that you can provision Serverless projects on a section level), I would recommend removing the applies_to tag altogether. Here's why:

  • The page-level metadata already includes the serverless: ga tag, which signals that all sections on this page are applicable in a Serverless context unless stated otherwise (for example the ECCTL section).
  • The page-level metadata also includes the ECH tag, which implies that all section are applicable in that context unless specified otherwise. So we'd only need to mark something as unavailble (the outlier sections on the page). Because our changes want to signal availability, we would default to the page-level tags.

I know the tagging can be a bit confusing, so hope that helps, but please feel free to reach out for more information or whenever you're unsure. 💟

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It makes total sense. Thank you @yetanothertw for the very detailed explanation!
I will make sure to keep this in my mind for the future doc related work too. 🙏
I will make a commit to remove the tag.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done the new commit: 3b67fe4

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can confirm the tags are removed as expected ^ ^
image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will merge the PR since we have addressed all the action items. Thank you @yetanothertw again for the valuable inputs! 🙇

```

:::{include} /deploy-manage/deploy/_snippets/tpec.md
Expand Down
Loading