-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Indenting correction for module configuration example #26604
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
Pinging @elastic/integrations (Team:Integrations) |
hi @robin13 , nice catch , we first update https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/azure/_meta/docs.asciidoc then run |
Hi @narph I don't have the whole build environment for beats set up, and it's a bit daunting for me to do this just for a typo fix... |
This pull request is now in conflicts. Could you fix it? 🙏
|
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
* Removed outdated documentation * Typo fix * Corrected indenting for module configuration example * Made changes in the _meta directory * mage update * changelog Co-authored-by: narph <mariana@elastic.co> (cherry picked from commit abf329b)
* Removed outdated documentation * Typo fix * Corrected indenting for module configuration example * Made changes in the _meta directory * mage update * changelog Co-authored-by: narph <mariana@elastic.co> (cherry picked from commit abf329b) Co-authored-by: Robin Clarke <robin.clarke@elastic.co>
* Removed outdated documentation * Typo fix * Corrected indenting for module configuration example * Made changes in the _meta directory * mage update * changelog Co-authored-by: narph <mariana@elastic.co>
What does this PR do?
Fix YAML indenting for module configuration example
Why is it important?
The example given was invalid
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 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
.Author's Checklist