Update a Namespace With Optimistic Concurrency
A 3-step recipe with Temporal. We can help you get access.
Recipe · 3 steps
Update a Namespace With Optimistic Concurrency
with Temporal · Tenant Provisioning & Lifecycle
Safely update a Namespace spec using its current resourceVersion.
- Read the Namespace to capture its current resourceVersion, required to perform an optimistic-concurrency update.
- Submit the new spec carrying the resourceVersion just read so the control plane can reject the change if the Namespace was modified concurrently.
- Re-read the Namespace to confirm the update was applied and surface the new resourceVersion.
What you'll need to have ready
- bearerToken: API key used as the Bearer token for Authorization.
- namespace: The Namespace identifier to update.
- spec: The full replacement Namespace spec object.
For your developer
Arazzo workflow temporal:update-namespace, 3 operations: getNamespace → updateNamespace → getNamespace. Specs on APIs.io.