biguery: Fix Table does not have Schema failures in Tests#16517
Merged
BBBmau merged 1 commit intoMar 4, 2026
Conversation
Collaborator
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Collaborator
Tests analyticsTotal tests: 150 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Collaborator
wj-chen
approved these changes
Mar 3, 2026
Member
wj-chen
left a comment
There was a problem hiding this comment.
Thanks for the fix. Looks to be an API validation update that now enforces that base table for the row access policy must have a schema.
melinath
approved these changes
Mar 4, 2026
This was referenced Mar 4, 2026
aditikumarii-google
pushed a commit
to aditikumarii-google/magic-modules
that referenced
this pull request
Mar 10, 2026
ChuAmberZhang
pushed a commit
to ChuAmberZhang/magic-modules
that referenced
this pull request
Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes hashicorp/terraform-provider-google#26111
Fixes hashicorp/terraform-provider-google#26115
This may be a temporary fix as it remains unclear why the tests began to fail in the first place. From my initial investigation comment:
This error comes from
bigquery_tablewith the following error:initially thought this was from a
go.modbump asintroduced cloud.golang bump where the first failure began. This doesn't seem like the cause as when I revert the bump we still run into the same issue
TeamCity Build:
https://hashicorp.teamcity.com/test/5962285105755560780?currentProjectId=TerraformProviders_GoogleCloud_GOOGLE_NIGHTLYTESTS
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.