-
Notifications
You must be signed in to change notification settings - Fork 43
Remove "effective_on" from trusted_tasks #2630
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
Conversation
|
The acceptance timeout should be fixed if you give it a rebase. |
5115a99 to
d535558
Compare
Thanks! Now the current failure is due to my changes. Pushing a new commit, apologies. |
simonbaird
left a comment
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.
See my comments and questions.
4eac6b4 to
76eddb6
Compare
|
acceptance tests failed on: and konflux build PLR failed on unrelated issue, retesting: |
|
/retest |
simonbaird
left a comment
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, apart from the "backwards compatibility" suggestion.
|
Nice patch! |
a2b23f0 to
e675723
Compare
- Remove effective_on field from taskRecord struct - Replace effective_on logic with expires_on-only approach - Most recent record (index 0) have no expires_on (always valid) - Previously demoted records get expiry based on demotion time + inEffectDays - Use --in-effect-days flag to set expiry of relevant records - Update all tests to reflect new expires_on-only behavior resolves: EC-423
|
Merging this since I addressed all the comments and got approvals. |
resolves: EC-423