-
Notifications
You must be signed in to change notification settings - Fork 185
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
Alerting Plugins #93
Alerting Plugins #93
Conversation
Looks like lint is failing, can you take a look @arnavdas88? |
@stockholmux Yup... Checking the code.... |
@arnavdas88 Can't tell you what's going on with some of these failures, but the DCO check failing is straight forward - I like this guide for fixing DCO issues. |
Actually, 2 of the commits in between didn't take the '--signoff' switch for some reason... I am doing some rebase to fix the issue!! Sorry for the inconviniance Actually, 2 of the commits in between didn't take the '--signoff' switch for some reason... I am doing some rebase to fix the issue!! Sorry for the inconviniance |
Now the previously unsigned commits are gone... so hopefully, it should work now!!! |
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 your contribution. 👍
Overall looks good, there are, however, two issues that I would like to ask to change:
- CI lint currently is failing because stubs are located in the incorrect path, e.g.
out/opensearchpy/plugins/alerting.pyi
instead ofopensearchpy/plugins/alerting.pyi
- It would be cool if you squash commits into one or prepare a meaningful list of commits in the PR. Of course, squash could be done by the person who will merge this, but it is always better to be done by the author.
P.S. Integration tests are failing because of #97 for sure.
edit: we probably will benefit from some regression tests checking that alerting plugin is called correctly, but this could be done separately.
@@ -0,0 +1,7 @@ | |||
from ..plugins.alerting import AlertingClient as AlertingClient |
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.
please add license header
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.
Need license headers here.
@VijayanB Give me a few minutes... i will apply the changes... |
@VijayanB , I have squashed and pushed new commits with "license headers" and "removed warnings". Could you please check if the issues you pointed are solved or not. |
@arnavdas88 There are now 18 commits that are not good to push into |
Squashed into 1 single commit... Finally... 😆 |
Signed-off-by: Arnav Das <[email protected]>
Signed-off-by: Arnav Das <[email protected]>
@arnavdas88 shall we add alerting to async as well? |
@arnavdas88 @VachaShah @dblock the only check failing is whitesource which is addressed here. The issue is not relevant here as we're building the right versions of the library where appropriate and is harmless against older versions that still use it. Also, @arnavdas88 we should be incrementing the version to |
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.
I am good with this! Any objections anyone else? Will wait a few days to hear back and/or merge.
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.
Thank you @arnavdas88 for this feature!
# | ||
# Licensed to Elasticsearch B.V. under one or more contributor | ||
# license agreements. See the NOTICE file distributed with | ||
# this work for additional information regarding copyright | ||
# ownership. Elasticsearch B.V. licenses this file to you under | ||
# the Apache License, Version 2.0 (the "License"); you may | ||
# not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, | ||
# software distributed under the License is distributed on an | ||
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
# KIND, either express or implied. See the License for the | ||
# specific language governing permissions and limitations | ||
# under the License. |
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.
Can you remove this and other places where is this introduced?
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.
Right. If it's new code added after the fork we don't carry the ES license anymore.
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Hi @arnavdas88 I forgot to remove some elastic licenses on files that have been added since the fork. Can you merge arnavdas88#2. Thanks. |
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Remove elastic search licenses on new files
Thankyou @harshavamsi for fixing these issues in the code!!! I have merged the PR so you can run the workflow again... |
@@ -97,7 +98,7 @@ def __init__( | |||
http_compress=None, | |||
opaque_id=None, | |||
loop=None, | |||
**kwargs, | |||
**kwargs |
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.
nit: Was this change introduced by styling tool? If not, can you revert here and other places? Thanks
""" | ||
Acknowledges an alert. | ||
|
||
:arg monitor_id: The id of the monitor, the alert belongs to |
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.
nit: Doc doesn't reflect all parameters
@@ -24,6 +24,7 @@ | |||
# specific language governing permissions and limitations | |||
# under the License. | |||
|
|||
|
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.
nit: if this is not introduced by styling tool, please revert this change.
@VijayanB Since the remaining items are nits, want to approve/merge? otherwise which ones are must haves? |
Merged 🎆 |
Signed-off-by: arnavdas88 [email protected]
Description
These commits are regarding the issue #90 . This is just the initial commit with
OpenSearch.plugins.alerting.*
.Issues Resolved
The issue of creating alerts from the python client.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.