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

Webhook on pacticipant tag #404

Open
konalegi opened this issue Mar 24, 2021 · 5 comments
Open

Webhook on pacticipant tag #404

konalegi opened this issue Mar 24, 2021 · 5 comments

Comments

@konalegi
Copy link

konalegi commented Mar 24, 2021

This is a question or feature request, is it possible in the current implementation of the broker to send a webhook when the participant has been tagged? If it's not can I do PR with this feature (any objections against it)?

@bethesque
Copy link
Member

Can you describe your usecase? Is it just when they've been deployed and are tagged with an environment, or is it when something is published with a particular tag, or it when the tag is created at any time?

Some info that might be relevant, and shape what you're asking for, is that these features will be coming out soon .

#403
#384
#382

@sagupta02
Copy link

Hello , I also have a use case for this feature.
For the case when consumer requests a new feature from provider , Currently there is no way to inform consumer back (via slack or else) that the specific feature pact has been implemented by providerand consumer can now merge the change.
Note : I have tried to use provider_verification_succeeded but that doesn't say anything about a particular feature tag .If I setup that Webhook to post a slack message to consumer , and If there are other provider builds (bug fix,refactoring) before the actual feature implementation then consumer won't know when the feature was implemented unless consumer checks pact broker matrix.

Also for the feature about adding participant tag , that can work if we follow a common branch naming strategy for new features, right?

@konalegi
Copy link
Author

@bethesque
Sorry, I should have described my use case firstly.
Our use case is to schedule a particular Jenkins job on application deployment, technically when production tag is created on the arbitrary participant. I think this discussion is closest to my needs #384. However having webhooks on tags will be more convenient in my case, because I don't need to change the current deployment workflow.
Thanks

@bethesque
Copy link
Member

Can you raise a feature request at pact.canny.io @konalegi

@konalegi
Copy link
Author

konalegi commented Apr 1, 2021

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