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

The lack of explicit connection between webhooks and workflows makes webhook errors hard to diagnose #567

Open
grahamalama opened this issue Jun 9, 2023 · 2 comments
Labels
enhancement New feature or request okr

Comments

@grahamalama
Copy link
Contributor

In Bugzilla, up to this point, we've created a new webhook per product. We have a naming convention of JBI-<environment>-<product>. For example:

Name Product Component
JBI-PROD-Core Core ANY
JBI-PROD-DataPlatformAndTools Data Platform and Tools ANY
JBI-PROD-DevTools DevTools ANY

In config, projects specify the Jira project they map to and what whiteboard tag they use. There is no information indicating which product or products a workflow uses.

This makes webhook errors hard to diagnose. For example, if I were to log in and see that the JBI-PROD-Core webhook had errors piling up and was disabled, I wouldn't have the information to know which project likely caused that blockage at a glance.

@leplatrem
Copy link
Contributor

Should we add the webhook name do the ActionContext? It would allow us to query BigQuery at least

@leplatrem
Copy link
Contributor

Is this relevant if we do #21 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request okr
Projects
None yet
Development

No branches or pull requests

3 participants