Cherry-pick #19981 to 7.x: [Filebeat][Gsuite] Make GSuite docs more clear#20066
Merged
marc-gr merged 1 commit intoelastic:7.xfrom Jul 27, 2020
Merged
Cherry-pick #19981 to 7.x: [Filebeat][Gsuite] Make GSuite docs more clear#20066marc-gr merged 1 commit intoelastic:7.xfrom
marc-gr merged 1 commit intoelastic:7.xfrom
Conversation
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
andrewkroh
approved these changes
Jul 20, 2020
daf56ff to
a1974c0
Compare
* Make GSuite docs more clear * Add links to help and summary * Convert filesets info to a table (cherry picked from commit f74745b)
a1974c0 to
6aab91a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry-pick of PR #19981 to 7.x branch. Original message:
What does this PR do?
After reading Gsuite docs for 7.9 I thought some things might benefit of a bit more info.
Why is it important?
Docs need to be as clear as possible for people who sets up the module.
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.