resource google_cloud_scheduler_job fails with "Error: Provider produced inconsistent final plan"

[gsouf]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version & Provider Version(s)

Terraform v1.9.6
on linux_amd64

• provider registry.terraform.io/hashicorp/google v6.4.0

Affected Resource(s)

google_cloud_scheduler_job

Terraform Configuration

resource "google_cloud_scheduler_job" "scheduler_job" {
  name        = "scheduler-job"
  description = "Triggers the Cloud Function scheduler"
  region      = var.region

  schedule  = "*/1 * * * *"
  time_zone = "UTC"

  retry_config {
    retry_count = 1
  }


  http_target {
    http_method = "GET"
    uri         = google_cloudfunctions_function.scheduler_function.https_trigger_url

    oidc_token {
      service_account_email = var.service_account_email
    }
  }

  depends_on = [google_cloudfunctions_function_iam_member.member]
}

Debug Output

No response

Expected Behavior

No response

Actual Behavior

Got error "which should be reported in the provider's own issue tracker" after re-applying terraform:

│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for module.scheduler.google_cloud_scheduler_job.scheduler_job to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/google" produced an
│ invalid new value for .http_target[0].oidc_token[0].audience: was null, but now cty.StringVal("https://us-central1-{*****}").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Steps to reproduce

1. terraform apply

Important Factoids

No response

References

No response