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

Have the possibility to define a custom webhook per container #1208

Open
ar3thien opened this issue Jul 2, 2024 · 1 comment
Open

Have the possibility to define a custom webhook per container #1208

ar3thien opened this issue Jul 2, 2024 · 1 comment

Comments

@ar3thien
Copy link

ar3thien commented Jul 2, 2024

Description

Is it possible to assess the possibility of having a custom webhook per container? the reasoning here, is that I need diun to trigger a CI pipeline when a new image become available. I have a pipeline per container, bcz I have different unit testing for different containers. For instance, instead of defining the webhook URL part of diun configuration, have it defined as a container label, and diun reads it, and act accordingly.

@whysi
Copy link

whysi commented Oct 15, 2024

This feature would be helpful for me too, I'm pretty much in the same situation and need a bit more flexibility on the notification side to trigger different CI pipelines based on the new base images provided by Microsoft/Alpine/etc , different webhooks for different images (without having to run more instances of diun) would be great.

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

3 participants