-
Notifications
You must be signed in to change notification settings - Fork 510
Update the Integrations doc guidelines to reflect the new template #14917
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
🔍 Preview links for changed docs |
|
@kgeller @mjwolf @haetamoudi
|
I forgot we already have updated that file with our first elastic-package change here. All the other files in the folder aren't relevant. Skipping the new issue 👍 |
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.
LGTM 👍
| * [What do I need to use this integration?](#idg-requirements) | ||
| * [How do I deploy this integration?](#idg-docs-setup) | ||
| * [Troubleshooting](#idg-docs-troubleshooting) | ||
| * [Performance and scaling](#idg-docs-performance-scaling) |
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.
The performance and scaling depends on the users underlying infrastructure. Currently, I am noticing the ingest architecture is shared for one of the integrations. Is this an optional section in the document?
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.
Ideally, all sections should be included where applicable and if there is relevant content.
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.
LGTM 🚀
This PR: