terraform-provider-google
terraform-provider-google copied to clipboard
Error: Provider produced inconsistent result after apply
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.6.6 on linux_amd64
- provider registry.terraform.io/hashicorp/google v4.84.0
- provider registry.terraform.io/hashicorp/google-beta v5.32.0
Affected Resource(s)
google_bigquery_table_iam_member
Terraform Configuration
terraform {
required_providers {
gcp = {
source = "hashicorp/google"
version = "~> 4.0"
}
}
backend "pg" {}
}
# Configure the GCP Provider
provider "gcp" {
project = "***-devops-sandbox"
}
Debug Output
module.iam-binding-table.data.google_project.project: Read complete after 3s [id=projects/umg-devops-sandbox]
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
- create
Terraform will perform the following actions:
module.iam-binding-table.google_bigquery_table_iam_member.member will be created
- resource "google_bigquery_table_iam_member" "member" {
- dataset_id = "ad_users"
- etag = (known after apply)
- id = (known after apply)
- member = "user:*****"
- project = "***-devops-sandbox"
- role = "roles/*****"
- table_id = "*****" }
Plan: 1 to add, 0 to change, 0 to destroy. module.iam-binding-table.google_bigquery_table_iam_member.member: Creating... ╷ │ Error: Provider produced inconsistent result after apply │ │ When applying changes to │ module.iam-binding-table.google_bigquery_table_iam_member.member, provider │ "provider["registry.terraform.io/hashicorp/google"]" produced an │ unexpected new value: Root object was present, but now absent. │ │ This is a bug in the provider, which should be reported in the provider's │ own issue tracker. ╵
Expected Behavior
module.iam-binding-table.google_bigquery_table_iam_member.member will be created
- resource "google_bigquery_table_iam_member" "member" {
- dataset_id = "*****"
- etag = (known after apply)
- id = (known after apply)
- member = "user:****"
- project = "*****"
- role = "roles/*****r"
- table_id = "*****" }
Actual Behavior
error without resource creation
Steps to reproduce
-
terraform apply
Important Factoids
No response
References
No response