fix: bypass access control for materialization transforms

[a-lider]

Problem

Endpoint materialization transforms run without a request user. If HogQL resolution needs warehouse tables/views in that trusted background path, resolving with normal request-scoped access control can fail because there is no user context.

Observed examples in Error tracking include the endpoint materialization transform stack under ResolutionError: Unknown table web_vitals_mv. That issue also contains older non-materialization occurrences, so this PR targets the materialization-transform path specifically.

Changes

Set bypass_warehouse_access_control=True while compiling HogQL for endpoint materialization transforms.

How did you test this code?

Tests

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

Docs update

No

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(endpoints): bypass access control fo..." | Re-trigger Greptile}

[greptile-apps]

Missing regression test for access-control bypass

There is no test that verifies _print_materialized_hogql (or build_endpoint_hogql) succeeds when warehouse access control is enabled and no user is present. A future refactor that removes or negates this flag would silently reintroduce the failure with no test catching it.

A targeted test in test_endpoint_materialization.py could mock Database.create_for to assert it is called with bypass_warehouse_access_control=True, or mock HogQLDatabaseSources.is_hogql_warehouse_access_control_enabled to True and confirm the materialization pipeline still returns a valid HogQL string.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[a-lider]

added test_materialization_transform_compiles_warehouse_table_without_user_context

[github-actions]

Small targeted fix setting a bypass flag for a userless materialization context; the flag name and comment clearly explain the intent. The bot comment about missing tests is a valid suggestion but not a showstopper.

[sakce]

@sakce approved this PR from Slack with Graphite

[stamphog]

Retaining stamphog approval — delta since last review classified as trivial_paths.

[veria-ai]

PR overview

All previously flagged issues have been addressed. No open security concerns remain on this pull request.

Security review

No open security issues remain on this pull request.

Fixed/addressed: 1 · PR risk: 0/10

New commits pushed (delta classified non_trivial_delta) — stamphog approval dismissed; re-review running automatically.

[github-actions]

No showstoppers. The PR fixes a security gap by threading user context through the materialization pipeline so warehouse ACL is enforced for user-triggered operations, while Temporal's userless internal rebuilds use an explicit bypass flag. The inline review concerns (all marked outdated) were addressed in the current diff, tests cover both enforcement and bypass paths.