BOLT-906 follow-up: trigger dbt prod run + re-sync Metabase Snowflake connection
blockedPR #51 (BOLT-906) merged 2026-05-12, PR #52 (ALL-884 dbt CI seed fix) merged 2026-05-13T19:16Z. devices_tag + devices_workspacedevicetag clean models are in TextureHQ/dbt main but need to land in Metabase for Grace.
Steps:
1. Check if scheduled dbt prod run auto-handled the new models since #51 merge (look for next nightly run or check airflow/dbt cloud).
2. If not auto-handled: manually trigger dbt prod run (dbt run --select +clean.devices_tag +clean.devices_workspacedevicetag).
3. Re-sync Metabase Snowflake connection to refresh schema (admin / databases / texture / sync schema button OR API call).
4. Verify Grace can see devices_tag and devices_workspacedevicetag in Metabase. Ping Grace + Sergey when confirmed.
May require Sergey for dbt prod creds or Metabase admin access.
Event Timeline
created
status_change
queued → in_progress
progress
Step 1 done — Scheduled dbt Cloud prod run auto-handled both new models. PRODUCTION.CLEAN.DEVICES_TAG (4760 rows) and PRODUCTION.CLEAN.DEVICES_WORKSPACEDEVICETAG (2117958 rows) were created as views on 2026-05-12 17:00 PDT (=2026-05-13 00:00 UTC) by dbt Cloud prod run invocation 3b9f07dd-c1eb-4378-89bf-c938605f1d78. Views compile and return data. Step 2 (manual trigger) NOT needed. Step 3 (Metabase resync) requires admin access I do not have — no Metabase creds in 1Password Fleet Secrets vault or local config. Metabase URL: https://metabase.texturehq.com/. Blocking on Sergey to either click Admin → Databases → Snowflake → Sync DB schema, or share an API key.
status_change
in_progress → blocked