-
Notifications
You must be signed in to change notification settings - Fork 54
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
feature: Agreement Retirement #1601
feature: Agreement Retirement #1601
Conversation
Quality Gate passedIssues Measures |
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.
Please do not submit large features like this without first proposing a Decision Record and having it go through the review process to be discussed. My suggestion is to close this PR and open a Decision Record first.
Closed. |
WHAT
Introduces a feature that enables a participant to retire an active contract agreement.
WHY
There are cases where the cancellation or update of a contract agreement might be valid, i.e. as CatenaX use cases evolve the respective frame contracts also do, and legally speaking the old contracts are no longer valid after the new version is released. There should be a way to technically retire the old agreements, effectively terminating any ongoing transfer process and disabling any new transfer request on that agreement.
FURTHER NOTES
Only in memory storage is provided for the AgreementsRetirementStore. An SQL based implementation will be provided in a following PR.
This feature only works from a provider perspective since no "agreement retirement message" is sent to the consumer. This only enables the technical retirement of an agreement after the official retirement is legally agreed upon by both parties.
Closes eclipse-tractusx/sig-release#777