Conversation
Allda
force-pushed
the
ISV-6109
branch
3 times, most recently
from
a5e5c51 to
2414c3b
Compare
kosciCZ
approved these changes
Aug 12, 2025
Contributor
kosciCZ
left a comment
kosciCZ
left a comment
There was a problem hiding this comment.
LGTM overall. Based on my reading of the code, I think that it is missing some kind of communication back to the user in the PR about their place in the queue/if the trigger fails.
However this MR seems more about deployment, so this is probably out of scope for that.
ezopezo
approved these changes
Aug 12, 2025
| @@ -107,7 +107,7 @@ security: | |||
|
|
|||
A dispatcher is a new component to manage incoming webhooks from Github. It accept new requests and manage a queue based on cluster capacity. A capacity is defined as a number of running pipelines in certain namespace. This simple metrics will provide a buffer mechanism for time periods when we receive a bunk releases of operators. The mechanism keeps pending requests in the database queue and only trigger related pipeline in case of free capacity. The solution is made of: - Rest API - Postgres database - Dispatcher - Capacity manager JIRA: ISV-6108 Signed-off-by: Ales Raszka <araszka@redhat.com>
This commit brings a deployment configuration for a new webhook dispatcher application. It consist of following parts: - postgres database - webhook dispatcher application - services, routes, secrets, pvc, configs The application deployment is fully driven by the Ansible. As part of the commit I also split the "local" user workspace into separate ansible inventory that share a data with stage but can be customized. JIRA: ISV-6109 Signed-off-by: Ales Raszka <araszka@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit brings a deployment configuration for a new webhook
dispatcher application.
It consist of following parts:
The application deployment is fully driven by the Ansible.
As part of the commit I also split the "local" user workspace into
separate ansible inventory that share a data with stage but can be
customized.
JIRA: ISV-6109
Merge Request Checklists