Failing test(s): TestAccBigQueryJob_bigqueryJobCopy*

[rileykarson]

Impacted tests

• TestAccBigQueryJob_bigqueryJobCopyExample
• TestAccBigQueryJob_bigqueryJobCopyTableReferenceExample

Affected Resource(s)

• google_bigquery_job

Failure rates

• 100% since 2024-04-17

Message(s)

Error: Invalid count argument
          on /opt/teamcity-agent/temp/buildTmp/plugintest2020011704/work2738438235/terraform_plugin_test.tf line 4, in resource "google_bigquery_table" "source":
           4:   count = length(google_bigquery_dataset.source)
        The "count" value depends on resource attributes that cannot be determined
        until apply, so Terraform cannot predict how many instances will be created.
        To work around this, use the -target argument to first apply only the
        resources that the count depends on.

Nightly build test history

• https://hashicorp.teamcity.com/test/-5211681911631249204?currentProjectId=TerraformProviders_GoogleCloud_GOOGLE_NIGHTLYTESTS&expandTestHistoryChartSection=true

b/336319185

[rileykarson]

This appears to have started failing based on a Terraform Core upgrade. I suspect it's just an issue with the test configuration where an earlier version of Core was less strict (but the actual behaviour was undefined).

[wj-chen]

I can repro locally. Adding depends_on didn't help. I'm guessing -target happens on the test setup side. Still investigating.

[rileykarson]

The issue here has to do with unknown values: https://developer.hashicorp.com/terraform/language/expressions/references#values-not-yet-known. Googling the error shows a lot of other results, as it's not really resource or provider specific.

The guidance to use -target only works interactively. You would replicate that in a test by breaking the Config step in two, applying dependencies first and then the remainder of the resources afterwards.

However, what I'd actually recommend here is storing the count value in a locals block and referencing it from both count fields, since we always want the count to be the same between the two resources. If that doesn't work, I'd just hardcode as 2 in both spots.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.