Idempotency keys for mutation endpoints

When using the api if a service crashes after the api request but before a database is updated with deployment id's, there is a risk that any retries will create duplicate deployments. With idempotency keys this is mitigated.

Workaround
-
Problem
-

Please authenticate to join the conversation.

Upvoters
Status

πŸ‘€ In Review

Board

πŸ’‘ Feature Requests

Tags

API

Date

About 2 hours ago

Subscribe to post

Get notified by email when there are changes.