Conversation
AI-Assisted: Cursor Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
lgtm. I smell lots of possibilities!
I think, to round this out, you would want to call out the CLI in these spots too:
- https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8277/deploy-manage/deploy/cloud-on-k8s/tools-apis
- https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8277/deploy-manage/deploy/cloud-enterprise/tools-apis
(similar to how we talk about cluster-level stuff in these pages)
and https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8277/reference to surface the new CLI reference wherever we have it sat
| :::{tip} | ||
| :applies_to: serverless: preview | ||
| For a command-line workflow, use the [Elastic CLI](cli://index.md) to run supported project operations. For an example of how to connect the CLI to {{ecloud}} and manage projects, follow [Connect to {{ecloud}} with the Elastic CLI](cli://cli/manage-elastic-cloud.md). | ||
| ::: |
There was a problem hiding this comment.
I'd prob move this one up above the resources heading, because these are all links to api reference material specifically, but this is closer to an alternative pathway to doing these operations. similar to the agent skill callout
| :::{include} /deploy-manage/deploy/_snippets/other-apis.md | ||
| ::: | ||
|
|
||
| ## Manage Elastic APIs with the Elastic CLI |
There was a problem hiding this comment.
I think "manage apis" is the wrong phrasing here because it's just another interaction layer - you're using the apis via the cli, not managing them. I'd prob simplify down to just a product title, similar to the console entry and the ecctl entry
| ## Manage Elastic APIs with the Elastic CLI | |
| ## Elastic CLI |
alt that is not better
| ## Manage Elastic APIs with the Elastic CLI | |
| ## Elastic Cloud through Elastic CLI |
There was a problem hiding this comment.
is "reuses" the right word here? makes it seem a little insecure
do we want to say all of the operations here, or can we just say "all of the operations"?
2 participants
Summary
clirepository forcli://cross-repository links.Dependencies
This PR must not be merged until both of these PRs are merged:
Related to elastic/docs-content-internal#1154.
Validation
git diff --checkpasses.docs-builderresolves all addedcli://index.mdlinks.Generative AI disclosure
Made with Cursor