Skip to content
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

Open
simonsigre opened this issue Feb 2, 2018 · 5 comments
Open

v1 REST API Decommissioning #116

simonsigre opened this issue Feb 2, 2018 · 5 comments

Comments

@simonsigre
Copy link

How does the following timeline

On April 24, 2018, at 10 pm PST, our v1 REST API is entering a decommissioning period. Starting on that date, you will no longer be able to generate v1 REST API keys, but the v1 REST API will remain operational.

On October 19, 2018, at 10 pm, the v1 REST API will be decommissioned and no longer operational.

Impact users of pdagent ? When will pdagent be upgraded to support v2?

@simonsigre
Copy link
Author

simonsigre commented Feb 2, 2018

I have also now raised this with support

2018-02-02 03:32 AM PST
Transcript ID: whcyKvxIL49C801n3F4VK0E7D0S0SOF1
Your recent chat with Chiedu
You
Good evening; I have noted that https://github.com/PagerDuty/pdagent (which we use.. and seems to > be supported by PD) looks to be using the V.1 API
This looks to be decom'd in the next 2 months.. are there any plans to update pdagent to support v2?

Chiedu
I( believe so
Hello Simon

You
I have raised the following #116 But I fear this will not be resolved in time

Chiedu
Many thanks for bring it to our attention
I will take it up with the Team of Engineers later today and come back to you

You
Thank you

Chiedu
No problem Simon

You
I am happy to close this chat now, I really hope this is resolved oon
*soon

@JasonRaynar-sb
Copy link

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)

@jbaldo
Copy link

jbaldo commented Mar 29, 2018

Hey @JasonRaynar-sb, thanks for your message. Are you not able to open a pull request against this repo?

@JasonRaynar-sb
Copy link

JasonRaynar-sb commented Mar 29, 2018

@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.

@jbaldo
Copy link

jbaldo commented Mar 30, 2018

I'm looking at the documentation and it looks like it consumes a v1 Events API key. Can you confirm?
https://www.pagerduty.com/docs/guides/agent-install-guide/

The v1 Events API is not being decommissioned, but it would still be nice to add support for the v2 Events API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants