-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
location is set to null on terraform import for bigquery transfer config #12011
location is set to null on terraform import for bigquery transfer config #12011
Comments
The location is part of the {{name}} |
What's the latest status here? Thank you. |
any progress? |
Importing for us has |
OMG it still open! @zli82016 can you help here? |
Any updates? |
Hey team @zli82016 @edwardmedia @trodge @obada-ab any update here? |
Seems like an issue with the custom import code, working on a fix |
b/297498365 |
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. |
Community Note
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 tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
where
data_source_id = "google_cloud_storage"
Command
Expected Behavior
In resulting state file, location should be set appropriately - for eg.
"location": "US"
Actual Behavior
After import, location in state is set to null:
"location": null
This causes an issue, as now terraform plan shows it would need to recreate the resource:
Same message is shown if location is set to null or "US" in tf file.
The text was updated successfully, but these errors were encountered: