-
Notifications
You must be signed in to change notification settings - Fork 181
Update ece-restore-snapshots-into-new-deployment.md #3763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Documented the fact that only snapshots from the `found-snapshots` repository are allowed and the restore can't be made from a custom repository.
🔍 Preview links for changed docs |
yetanothertw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing this!
I suggest adding an important admonition to add visibility and weight to your point.
|
|
||
| 1. First, [create a new deployment](../../deploy/cloud-enterprise/create-deployment.md) and select **Restore snapshot data**. Select the deployment that you want to restore a snapshot *from*. If you don’t know the exact name, you can enter a few characters and then select from the list of matching deployments. | ||
| 2. Select the snapshot that you want to restore from. If none is chosen, the latest successful snapshot from the cluster you selected is restored on the new cluster when you create it. | ||
| *Please note that only snapshots from the `found-snapshots` repository are accepted. Snapshots from a custom repository are not allowed.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This addition seems important enough to warrant an admonition for emphasis. Perhaps something like this?
| *Please note that only snapshots from the `found-snapshots` repository are accepted. Snapshots from a custom repository are not allowed.* | |
| :::{important} | |
| Note that only snapshots from the `found-snapshots` repository are accepted. Snapshots from a custom repository are not allowed. | |
| ::: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the addition, the important section gives it more visibility
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I'll add the commit then if you don't mind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
|
Thanks so much for the reviews @yetanothertw! What's the best way to request a change to the naming? This page prefix is |
|
Hi @maggieghamry ,
Our source files use a tagging system to indicate which Elastic products and deployment models the content applies to. In the case of the Restore snapshot into a new deployment page, you can see that the page is tagged as applying both to ECE and ECH. These badges are visual indicators on the published page, signalling to users that it applies to both these products: You're right that Many thanks! 🙏 |


Documented the fact that only snapshots from the
found-snapshotsrepository are allowed and the restore can't be made from a custom repository.