-
Notifications
You must be signed in to change notification settings - Fork 5k
Extend multiline documentation with filestream syntax #31927
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Collaborator
cmacknz
reviewed
Jun 14, 2022
cmacknz
reviewed
Jun 14, 2022
cmacknz
reviewed
Jun 14, 2022
Pinging @elastic/obs-docs (Team:Docs) |
Co-authored-by: Craig MacKenzie <craig.mackenzie@elastic.co>
cmacknz
approved these changes
Jun 21, 2022
@Mergifyio backport 7.17 |
It seems this PR didn't get backported, l'm trying to backport it now. |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Jan 24, 2023
(cherry picked from commit 76eec5b)
belimawr
pushed a commit
that referenced
this pull request
Jan 24, 2023
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v7.16.0
Automated backport with mergify
backport-v8.0.0
Automated backport with mergify
backport-v8.1.0
Automated backport with mergify
backport-v8.2.0
Automated backport with mergify
backport-v8.3.0
Automated backport with mergify
docs
Team:Docs
Label for the Observability docs team
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds
filestream
parser
configuration to multiline examples.Why is it important?
Avoid user confusion.
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Closes #31578