-
Notifications
You must be signed in to change notification settings - Fork 78
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
Backend: Add Splunk as a backend provider #335
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
cd2e3dd
to
00f3339
Compare
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.
Thanks a lot for this Maxime! I really appreciate both the quality and comprehensiveness of the PR, and only detected a few minor changes/nitpicks.
FYI : commit is blocked by this for now : EDIT : I forced the commit with |
68d506a
to
044eead
Compare
Hello, |
Signed-off-by: Maxime Véroone <[email protected]>
044eead
to
b5a8189
Compare
@lvaylet All your review points have been treated. Let me know if you have further remarks. |
@mveroone Sounds good to me now. Thanks for your hard work and patience! |
* Backend: Add Splunk as a backend provider Signed-off-by: Maxime Véroone <[email protected]> * WIP reveiw --------- Signed-off-by: Maxime Véroone <[email protected]>
Pretty straightforward, even though it's somehow a new exercice for me to go that deep into the code.
The goal of that PR is to implement a new backend provider : Splunk.
Since their APIs are the same, it should work both with Splunk CLoud or Splunk Enterprise (on premises)
I've tested it against the later, but should be able to test with both if needs be.
All new features are documented in the right directories and tests & mocks were implemented.