Skip to content

Conversation

claudia-correia
Copy link
Contributor

This PR adds a note to the change-hardware.md docs, to remind customers that the target instance configuration must be compatible with the tier/resource they're updating.

@claudia-correia claudia-correia added the documentation Improvements or additions to documentation label Mar 13, 2025
@claudia-correia claudia-correia requested review from a team and yuvielastic March 13, 2025 11:28
Copy link
Contributor

@florent-leborgne florent-leborgne left a comment

Choose a reason for hiding this comment

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

👍 Thanks Cláudia!

Note: this version of the docs will go live the same day as the 9.0 release. Until then, the asciidoc docs in the cloud repo will remain live (in case this is an urgent addition and needs to be published now)

@florent-leborgne florent-leborgne enabled auto-merge (squash) March 13, 2025 11:32
@florent-leborgne florent-leborgne merged commit 36476af into elastic:main Mar 13, 2025
3 of 4 checks passed
@claudia-correia
Copy link
Contributor Author

@florent-leborgne Thanks for the review and the additional info. I don't think this is urgent. @yuvielastic Would it be OK to release this docs the same day as the 9.0 release? 🙂
(Also, I can't find the related asciidoc docs in the cloud repo. Maybe I'm missing something?)

@claudia-correia claudia-correia deleted the update-change-hardware-docs branch March 13, 2025 11:37
@florent-leborgne
Copy link
Contributor

Also, I can't find the related asciidoc docs in the cloud repo. Maybe I'm missing something?

Asciidoc files will remain in the cloud repo until up to the ms-122 branch. From ms-123 (and master), they're removed in favor of this repo (only some reference content remains in the cloud repo in branches ms-123+, in markdown).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants