-
Notifications
You must be signed in to change notification settings - Fork 16
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
Adopt AEP-155: Idempotency #77
Conversation
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.
couple comments. main question to me is about whether we should better define how long an idempotency key is valid for?
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.
I think my main nit at this point is about the guidance on a minimum (still don't see it).
Also I'd consider my comment on the formats accepted by idempotency key. But not going to block further.
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.
Replying with notes from yesterday's meeting.
* Adopt AEP-155: Idempotency * Address Yusuke's comments. * Update aep/general/0155/aep.md * lint * Qualify proto-specific guidance. * Update to reflect new common components and live discussion. * Minor rephrasing of list. * Clarify invalid `first_sent`. * Remove section about stale success responses.
* Adopt AEP-155: Idempotency * Address Yusuke's comments. * Update aep/general/0155/aep.md * lint * Qualify proto-specific guidance. * Update to reflect new common components and live discussion. * Minor rephrasing of list. * Clarify invalid `first_sent`. * Remove section about stale success responses.
This is a pretty straightforward adoption of Google's AIP-155. The only substantial change is the renaming of the field from
request_id
toidempotency_key
. See the new subsection of the Rationale section for an explanation.