Support idempotency - add mandatory eventId to Request about corellia HOT 7 CLOSED

this eventId will be a header parameter.

from corellia.

Sounds like a good idea.

We can generate those Idempotency keys like:

• for {{url}}/corellia/api/insurance/contracts/v1/documents: _<receipt|certificate> ( fe. TEST-MHT_receipt, TEST-MHT_certificate )
• for {{url}}/corellia/api/insurance/contracts/v1/ : _contract ( fe TEST-MHT_contract )
  ^ that should do the trick.

Are you planning to implement as HTTP request header: Idempotency-Key: <key>?

from corellia.

can we use one Idempotency-Key: <key> per all 3 requests?

from corellia.

the goal is to have a unique identification for A request (for idempotency and communication reasons). this results in the requirement, that each event (request) must have its own unique requestId. We propose following the Zalando guide to use a UUID

from corellia.

the goal is to have a unique identification for A request (for idempotency and communication reasons). this results in the requirement, that each event (request) must have its own unique requestId. We propose following the Zalando guide to use a UUID

can we assume that you are expecting Idempotency-Key as (RFC4122) formatted string?

from corellia.

@frank-baier : can we resolve and close this ticket? (IMHO: yes)

from corellia.

As answer to Rolands comment, regarding RFC4122:
yes as described above a UUID per request is fine.
Please be aware that for one contract with two documents we have three requests altogether, which means, that we have three different UUIDs.

from corellia.