-
Notifications
You must be signed in to change notification settings - Fork 29
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
v1 REST API Decommissioning #116
Comments
I have also now raised this with support
|
We're looking to implement the agent, I've done a (working) POC of using V2 api -test cases run & successful trigger/resolves. Added mandatory fields for pd-send -s(severity) and -src(source) to meet V2 requirements ) - is there a place I can push these for review/to be included. Reluctant to use current pd_agent as don't want to invest in a deprecated API. Have changes on local clone of repo - happy to push up branch (event2ApiAgent) |
Hey @JasonRaynar-sb, thanks for your message. Are you not able to open a pull request against this repo? |
@jbaldo Forked and made a PR - hope that helps (or at leasts given quick way to use V2 api) - rather simple update but aimed to be minimally invasive. |
I'm looking at the documentation and it looks like it consumes a v1 Events API key. Can you confirm? The v1 Events API is not being decommissioned, but it would still be nice to add support for the v2 Events API. |
How does the following timeline
Impact users of pdagent ? When will pdagent be upgraded to support v2?
The text was updated successfully, but these errors were encountered: