Bump metabase provider to 0.14.2 (fix permissions_graph unmarshal, unblock deploys)#104
Conversation
The WA (Washington) tenant Terraform config was merged to main before the tenant was deploy-ready, causing terraform-apply on main to fail while provisioning ~51 WA resources. Because Terraform applies all-or-nothing per run, this blocked ALL main deploys to Metabase — including the benefit-card perf fix (#101), which is correct but stuck behind the failing apply. Reverting the WA config restores main to a cleanly-applyable state so #101 and future changes deploy. WA dashboard work should land via its own branch once the WA tenant (Metabase DB, permission groups, secrets) is fully set up and the apply is verified. Also removes stray .DS_Store files committed with that change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…marshal terraform-apply on main started failing today at metabase_permissions_graph.graph: Error: Unexpected error while calling the Metabase API for 'get permissions graph'. json: cannot unmarshal object into Go struct field PermissionsGraphDatabasePermissions.groups.create-queries Provider 0.14.1 only modeled `create-queries` as a scalar string, but Metabase returns it as an OBJECT once a group is granted granular (per-schema/per-table) create-query permissions via the Admin Permissions UI. So a UI permissions change (not a repo change) made the provider fail on state refresh, blocking ALL prod deploys — including the already-merged benefit-card perf fix (#101). Provider 0.14.2 fixes exactly this (changelog: "Handle create_queries as either a simple string or a serialized JSON object"). The `~> 0.14` constraint already allowed it; the lockfile was pinned to 0.14.1. Bumped constraint to `>= 0.14.2, ~> 0.14` and refreshed the lock for linux_amd64 (CI) + darwin_arm64. Unblocks deploys; no permissions.tf change needed (the granular UI perms are now parsed correctly rather than reverted). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 47 minutes and 8 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository: MyFriendBen/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (10)
Note
|
Terraform Plan 📖Show Plandata.external.metabase_ids: Reading...
Planning failed. Terraform encountered an error while generating this plan.
Error: Failed to create the Metabase client from username and password.
with provider["registry.terraform.io/flovouin/metabase"],
on metabase.tf line 2, in provider "metabase":
2: provider "metabase" {
received unexpected response from the Metabase session API
Error: External Program Execution Failed
with data.external.metabase_ids,
on permissions.tf line 150, in data "external" "metabase_ids":
150: program = ["python3", "${path.module}/scripts/get_metabase_ids.py"]
The data source received an unexpected error while attempting to execute the
program.
Program: /usr/bin/python3
Error Message: Creating Metabase session failed with HTTP 503: Service
Unavailable
State: exit status 1
Pusher: @catonph, Action: |
1 participant
Why
After #103 (the WA revert) merged, terraform-apply on main still failed — this time at 'metabase_permissions_graph.graph':
'''
Error: ... 'get permissions graph'
json: cannot unmarshal object into Go struct field ... create-queries
'''
Provider 0.14.1 only modeled 'create-queries' as a scalar string. Metabase returns it as an object once a group has granular (per-schema/table) create-query permissions set via the Admin Permissions UI. A UI permissions change (not a repo change) made the provider fail on state refresh, blocking all prod deploys — including the already-merged benefit-card perf fix (#101).
Fix
Bump 'flovouin/metabase' 0.14.1 → 0.14.2. Its changelog fixes exactly this: "Handle create_queries as either a simple string or a serialized JSON object." Constraint '~> 0.14' already allowed it; the lockfile was pinned. Updated constraint to '>= 0.14.2, ~> 0.14' and refreshed the lock for linux_amd64 (CI) + darwin_arm64.
No 'permissions.tf' change — the granular UI perms are now parsed correctly instead of needing to be reverted.
Result
Unblocks terraform-apply so #101 (and everything since) deploys to Metabase.
🤖 Generated with Claude Code