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

Fail pagerduty automations if projects aren't Pagerduty services #108

Open
in-op opened this issue Sep 13, 2024 · 0 comments
Open

Fail pagerduty automations if projects aren't Pagerduty services #108

in-op opened this issue Sep 13, 2024 · 0 comments

Comments

@in-op
Copy link
Contributor

in-op commented Sep 13, 2024

Currently the pagerduty automations to create service associations or remove them will exit early (considered a success) if either project does not exist in Pagerduty. Since the user flipped the switch, they probably expect the services are in there, and we should fail in these cases and tell the user that the project doesn't exist. Then they can determine if they want to add it to Pagerduty first or skip that automation.

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

1 participant