-
Notifications
You must be signed in to change notification settings - Fork 0
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
AIP-8622 v1.8.0 argo controller to support DLQ feature #7
Conversation
- without Sensor dlq, a feature in v1.9 (cherry picked from commit 2451789)
83d3e94
to
5abca59
Compare
by the looks of it your new branch is strictly based off the argo-events tag you are targeting and seems to build all the distributable in the makefile. I found in the past build the dists we do not need lead to a build of over 2 hours. I suggest commenting out those builds like here so the builds do not take long. |
is basing this branch off |
Yes, more details about avoiding the upgrade issue here: |
(cherry picked from commit 17070e7)
thank you! I cherry-picked 17070e7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm thanks for making the changes
I'm not understanding how the DLQ trigger works with these code. Should changes in |
This cherry pick doesn't include that code block with DlqTrigger into Sensor which is already on v1.9.2 of argo-events, it focuses on the controller and webhook validation. To include that code I'd also have to cherry pick other Sensor features in the 1.9 branch |
Building a patched release of Argo 1.8.1 with cherrypick of argoproj@2451789 feat(EventSensor): Dead Letter Queue Trigger (argoproj#3199)
notice: That this is against created
feature/zg-1.8
branch that is atargo-events
tag1.8.0
that is the version currently running in the cluster (see code link)