-
Notifications
You must be signed in to change notification settings - Fork 159
Clean up raw migrated files used in Troubleshoot section #778
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
thanks @marciw ! @shainaraskas , I see the page is mapped in both places:
In my opinion the page belongs to deploy and manage, as it's about filtering deployments (can be useful in troubleshooting to filter unhealthy deployments) but it's not directly related with troubleshooting at all. The title is misleading so we can also update the title and remove the Where should we fix this? If we agree I can create a quick PR and remove the duplicated mapping. |
Shaina and I already discussed this during the mapping phase, and it's in the spreadsheet with both mappings... in the troubleshooting section, the page is called "Finding deployments" and we have plans to tailor it. Happy for you to do whatever you like in D&M though of course :) |
we need to remove the duplicated |
gotcha. @eedugon the #784 removes the mapping from the troubleshooting file |
Prefer [the D&M page](https://github.com/elastic/docs-content/blob/main/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md) rather than the troubleshooting page. We have intentionally duplicated content in the troubleshooting section (for now). see #778 (comment)
Double-check raw migrated files used in the Troubleshoot section and delete the ones we don't need anymore.
@shainaraskas one fyi for you: I confirmed that
ece-find-md
is now represented in both Troubleshoot and Deploy & Manage, according to our divine mappings 🔮