Skip to content

CROSSLINK-264 retry-action#622

Draft
adamdickmeiss wants to merge 2 commits into
mainfrom
CROSSLINK-264-ask-retry-action
Draft

CROSSLINK-264 retry-action#622
adamdickmeiss wants to merge 2 commits into
mainfrom
CROSSLINK-264-ask-retry-action

Conversation

@adamdickmeiss
Copy link
Copy Markdown
Contributor

Copilot AI review requested due to automatic review settings May 29, 2026 11:58
@adamdickmeiss adamdickmeiss marked this pull request as draft May 29, 2026 11:58
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds retry-related entries to the returnables patron-request state model for CROSSLINK-264, introducing a requester-side retry event and supplier-side retry action.

Changes:

  • Adds accept-retry event on requester SENT, transitioning to NEW.
  • Adds ask-retry action on supplier VALIDATED, transitioning to NEW.
  • Keeps generated runtime JSON in sync with misc/returnables.yaml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
misc/returnables.yaml Adds retry event/action declarations to the source state model.
broker/patron_request/service/statemodels/returnables.json Updates the generated embedded runtime state model with the same retry declarations.

Comment thread misc/returnables.yaml
Comment on lines +51 to +53
- name: accept-retry
desc: Supplier accepts retry with new metadata
transition: NEW
Comment thread misc/returnables.yaml Outdated
Comment on lines +238 to +241
- name: ask-retry
desc: Ask requester to retry with new ISO18626 metadata
transitions:
success: NEW
(yes, tests do not pass)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants