John Spray b3bb1d1cad storage controller: make direct tenant creation more robust (#7247) ...

## Problem

- Creations were not idempotent (unique key violation)
- Creations waited for reconciliation, which control plane blocks while
an operation is in flight

## Summary of changes

- Handle unique key constraint violation as an OK situation: if we're
creating the same tenant ID and shard count, it's reasonable to assume
this is a duplicate creation.
- Make the wait for reconcile during creation tolerate failures: this is
similar to location_conf, where the cloud control plane blocks our
notification calls until it is done with calling into our API (in future
this constraint is expected to relax as the cloud control plane learns
to run multiple operations concurrently for a tenant)

2024-03-26 16:57:35 +00:00

..

migrations

storage controller: tech debt (#7165)

2024-03-19 16:08:20 +00:00

src

storage controller: make direct tenant creation more robust (#7247)

2024-03-26 16:57:35 +00:00

Cargo.toml

storage controller: tighten up secrets handling (#7105)

2024-03-25 11:52:33 +00:00