Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BigQuery Tables re-creating #8352

Closed
Dhanabalan-pop opened this issue Feb 1, 2021 · 3 comments
Closed

BigQuery Tables re-creating #8352

Dhanabalan-pop opened this issue Feb 1, 2021 · 3 comments
Assignees
Labels

Comments

@Dhanabalan-pop
Copy link

Dhanabalan-pop commented Feb 1, 2021

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 the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

We are using docker image: docker:18.09
Provider versions:
provider.google-beta: version = "~> 3.54"
So it should be latest terraform

Affected Resource(s)

  • google_bigquery_table

Terraform Configuration Files

  project = var.pop_project
  dataset_id = var.pop_dataset_name
  table_id   = "TEST"
  schema = file("modules/resources/schemas/TEST.schema.json")
}

Debug Output

terraform plan output:
~ {

+ mode = "NULLABLE"

name = "Test3"
type = "INTEGER"
} # forces replacement,
~ {
#+ mode = "NULLABLE"
name = "Test2"
type = "STRING"
} # forces replacement,
~ {
#+ mode = "NULLABLE"
~ name = "Test" -> "Test1"
~ type = "DATE" -> "INTEGER"
} # forces replacement,
~ {

+ mode = "NULLABLE"

~ name = "Test1" -> "Test"
~ type = "INTEGER" -> "DATE"
} # forces replacement,

Panic Output

Expected Behavior

Nothing should be destroyed

Actual Behavior

It is showing table will be destroyed and created

Steps to Reproduce

  1. terraform plan

Important Factoids

References

Schema File
"mode": "NULLABLE",
"name": "Test3",
"type": "INTEGER"
},
{
"mode": "NULLABLE",
"name": "Test2",
"type": "STRING"
},
{
"mode": "NULLABLE",
"name": "Test",
"type": "INTEGER"
},
{
"mode": "NULLABLE",
"name": "Test1",
"type": "DATE"
},

  • #0000
@ghost ghost added the bug label Feb 1, 2021
@Dhanabalan-pop
Copy link
Author

Not sure why it is adding mode:nullable

@venkykuberan venkykuberan self-assigned this Feb 1, 2021
@venkykuberan
Copy link
Contributor

Fix is coming as mentioned here #8337. Please reopen it if you are seeing the same issue after the fix.

@ghost
Copy link

ghost commented Mar 5, 2021

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Mar 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants