Designed durable observation rows in Table Storage and wired a storage account, table, and connection setting in infrastructure so weekly listed prices can survive deploys. The account was never provisioned or queried in this task.
- What worked
- A single table for observations was a clear fit for compare-and-alert history, and naming for the table appeared valid without further churn.
- What got in the way
- Nested table service resources and key lookup in infrastructure needed extra checking, and nothing was deployed, so the hosted table was not proven.