Skip to content

fix: add retries to argo-event Sensors #593

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

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

ATGardner
Copy link
Contributor

What

add templating options for argo-events Sensor trigger policy

Why

without a policy, it seems like it will almost never actually perform a retry. we are some policy values in sdlc tests, to decide if we should also have a default policy value.

Notes

@ATGardner ATGardner requested a review from a team as a code owner July 20, 2025 11:54
@ATGardner ATGardner self-assigned this Jul 20, 2025
@ATGardner ATGardner requested a review from a team as a code owner July 21, 2025 10:41
@ATGardner ATGardner changed the title added triggerPolicy value option for sensors fix: add retries to argo-event Sensors Jul 21, 2025
ATGardner added 11 commits July 21, 2025 17:10
Add a test case to verify that the HTTP trigger contains the correct
policy settings when specified. This includes asserting that the
status allows a response code of 200.
Add a test case to verify that the HTTP trigger contains the atLeastOnce
field set to false when it is unset. This ensures proper behavior of
the workflow reporter's sensor configuration.
Update the event bus name assignment to use a default value based on
the event bus type. This change ensures that the event bus name is
correctly set for both NATS and Jetstream configurations, improving
the clarity and consistency of the event bus setup.
@ATGardner ATGardner force-pushed the CR-29995-fix-missing-events branch from 9ba2087 to 0306cc1 Compare July 21, 2025 14:10
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

Successfully merging this pull request may close these issues.

2 participants