service_account_name is set to null on terraform import for bigquery transfer config

[anderssonpof]

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

Terraform v1.2.4
on linux_amd64
+ provider registry.terraform.io/hashicorp/google v4.34.0
+ provider registry.terraform.io/hashicorp/google-beta v4.34.0

Affected Resource(s)

google_bigquery_data_transfer_config

Expected Behavior

In resulting state file, location should be set appropriately - for eg. "service_account_name" : bq-transfer-sa@<PROJECT_ID>dev.iam.gserviceaccount.com

Actual Behavior

After import, service account name in state is set to null: "service_account_name": null

This causes an issue, as now terraform plan shows it would need to recreate the resource:

$ terraform plan
...
+ service_account_name     = "bq-transfer-sa@<PROJECT_ID>.iam.gserviceaccount.com" # forces replacement
...

Steps to Reproduce

1. create resource google_bigquery_data_transfer_config with service account specified

   bq mk \
      --transfer_config \
      --project_id="${PROJECT_ID}" \
      --data_source=google_cloud_storage \
      --display_name="${NAME}" \
      --target_dataset="${TARGET_DATASET}" \
      --service_account_name="${BQ_TRANSFER_SERVICE_ACCOUNT}" \
      --params="${PARAMS}" \
      --schedule="${TRANSFER_SCHEDULE}"

2. import resource google_bigquery_data_transfer_config
3. terraform plan

b/321386847

[edwardmedia]

@melinath would you call this is an api issue? Below is where the service_account is in the response body. ownerInfo is not defined anywhere in the resource.

{
  ...
  "ownerInfo": {
    "email": "myserviceaccount@smyproject.iam.gserviceaccount.com"
  }
}

[melinath]

hm, that's weird. serviceAccount is what you use to set this value on create but on read it shows up in ownerInfo.... but it looks like the ownerInfo might also be a non-service-account user? So I don't think we can always assume that field is a service account. But maybe it would still make sense to map it over on import specifically?

I'm not sure what the best thing to do here is.