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

Pagerduty API v1 is being deprecated #50

Open
kaivanov opened this issue Sep 13, 2018 · 3 comments
Open

Pagerduty API v1 is being deprecated #50

kaivanov opened this issue Sep 13, 2018 · 3 comments

Comments

@kaivanov
Copy link

Does this support the Pagerduty v2 API ?

@majormoses
Copy link
Member

We are pinned on https://github.com/sensu-plugins/sensu-plugins-pagerduty/blob/4.0.0/sensu-plugins-pagerduty.gemspec#L32 but inspecting the upstream code I don't think it does. I then saw this: envato/pagerduty#52 which I will try to find some to review this weekend and try to get in touch with the upstream maintainer. /cc @jspaleta to see if maybe you can be some extra 👀 and reach out that would be good.

@majormoses
Copy link
Member

Will need to take note of the breaking changes that we will need to account for once its been accepted upstream.

@majormoses
Copy link
Member

So it turns out that the upstream gem is using the events v1 api not the REST v1 api so it will be supported post Oct 19th

This change only affects the v1 REST API. You can continue to use the v1 Events API as you do today.Learn more about our the differences between our APIs here.

https://v2.developer.pagerduty.com/docs/v1-rest-api-decommissioning-faq#section-will-the-v1-events-api-still-be-supported-

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

No branches or pull requests

2 participants