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

Where do I get PD_VENDOR_KEY ? #303

Closed
gsiddardha opened this issue Nov 21, 2019 · 6 comments
Closed

Where do I get PD_VENDOR_KEY ? #303

gsiddardha opened this issue Nov 21, 2019 · 6 comments

Comments

@gsiddardha
Copy link

Hi,

I'm trying to setup healthchecks on my system with PD integration. This requires PD_VENDOR_KEY value to be set. I am not able to find any documentation on pagerduty website on how to get this value. Can someone please help point me to the right documentation?

@cuu508
Copy link
Member

cuu508 commented Nov 21, 2019

PD_VENDOR_KEY is needed for PagerDuty Connect, a mechanism for authorizing an integration to access user's PagerDuty account.

From https://www.pagerduty.com/docs/guides/pagerduty-connect/

vendor: A unique identifier for the partner. Please contact support for your vendor key.

I got my vendor key after filling out a "Become a Partner" form somewhere on their site (this was a while ago, not sure if the process would be the same now).

For private self-hosted installations becoming a partner might not be feasible, but it should be possible to use PagerDuty API without using PagerDuty Connect. In fact, this is how the integration used to work before I implemented PagerDuty Connect here:

96e00df

Ideally Healthchecks would use the old way if PD_VENDOR_KEY is not set, and PagerDuty Connect if PD_VENDOR_KEY is set.

@gsiddardha
Copy link
Author

Got it.

Currently healthchecks also has a restriction on the key to be non-null, to allow PD integration.

  1. Enable PD integration only if enable_pd
  2. Set enable_pd to false if PD_VENDOR_KEY is None

I guess I can manually add a Channel entry with kind = pd as a hack for now. Please correct me if I'm wrong.

@cuu508
Copy link
Member

cuu508 commented Nov 21, 2019

Ah yes, that would be a clever workaround for time being. When creating the Channel, the value field needs to look like so:

{"service_key": "api key here", "account": "name of the account for display"}

@gsiddardha
Copy link
Author

cool. got it working. thanks for the support.

Any thoughts on how we can manage this better? instead of manually adding a channel for each new project.

@cuu508
Copy link
Member

cuu508 commented Nov 22, 2019

Any thoughts on how we can manage this better? instead of manually adding a channel for each new project.

I'm working on supporting both the old onboarding flow where the user supplies an API key, and the PagerDuty Connect one (if PD_VENDOR_KEY is set).

@cuu508 cuu508 reopened this Nov 22, 2019
@cuu508
Copy link
Member

cuu508 commented Nov 22, 2019

This is now implemented – you can now add a PagerDuty integration without having the PD_VENDOR_KEY set.

@cuu508 cuu508 closed this as completed Nov 22, 2019
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

2 participants