Skip to content
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

[DOC] Add yml highlight and copy button to pipeline docs and fix config navigation for Data Prepper #8223

Open
1 of 4 tasks
vagimeli opened this issue Sep 11, 2024 · 0 comments
Assignees
Labels
1 - Backlog - DOC Doc writer assigned to issue responsible for creating PR. Sev4 A low priority issue. Can be addressed after all other severity levels are addressed.

Comments

@vagimeli
Copy link
Collaborator

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request.

  • Looking at the Data Prepper section, none of the yaml snippets have the yaml highlighter or copy button added.
  • The configuration directory seems unnecessary. Just want to flag this for a future fix. This just makes the link longer (and shorter links are preferable for SEO). We can fix that by removing the configuration folder and adding redirects from the old link to the new link in all files under the pipelines directory.

*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.

Current version

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@Naarcha-AWS Naarcha-AWS added 1 - Backlog - DOC Doc writer assigned to issue responsible for creating PR. and removed untriaged labels Sep 23, 2024
@Naarcha-AWS Naarcha-AWS added the Sev4 A low priority issue. Can be addressed after all other severity levels are addressed. label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DOC Doc writer assigned to issue responsible for creating PR. Sev4 A low priority issue. Can be addressed after all other severity levels are addressed.
Projects
None yet
Development

No branches or pull requests

2 participants