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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Salesforce BigQuery Transfer | Parameter Issue #18506

Open
RomeoAva opened this issue Jun 20, 2024 · 1 comment
Open

Salesforce BigQuery Transfer | Parameter Issue #18506

RomeoAva opened this issue Jun 20, 2024 · 1 comment

Comments

@RomeoAva
Copy link

RomeoAva commented Jun 20, 2024

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.5.7
on MacOS

  • provider registry.terraform.io/hashicorp/google v5.34.0

Affected Resource(s)

google_bigquery_data_transfer_config

Terraform Configuration

terraform {
  backend "gcs" {
    bucket = ""
    prefix = "terraform/state"
  }

  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "5.34.0"
    }
    random = {
      source = "hashicorp/random"
    }
  }
}

Debug Output

No response

Expected Behavior

Hello, I am trying to create a Salesforce Transfer for BQ using Terraform. Here is my current config to create that ressource:

resource "google_bigquery_data_transfer_config" "query_config" {
  display_name           = "import_salesforce"
  location               = "US"
  data_source_id         = "salesforce"
  destination_dataset_id = "analysis"
  params = {
    "connector.authentication.oauth.clientId"     = ""
    "connector.authentication.oauth.clientSecret" = ""
    "connector.authentication.username"           = ""
    "connector.authentication.password"           = ""
    "connector.authentication.securityToken"      = ""
    "assets"                                      = ["Project_ABC"]
  }
}

Actual Behavior

When specifying a list in the assets parameter, terraform tells me:

 Inappropriate value for attribute "params": element "assets": string required.

When I try to convert it to a String, the transfer is created but on BigQuery I get the following error:

Incorrect assets set in transfer config : string_value: "Project_ABC" , assets should be a non-empty list of strings.

I also tried to json_encode the list, but same result on BQ side:

Incorrect assets set in transfer config : string_value: "[\"Project_ABC\"]" , assets should be a non-empty list of strings.

Steps to reproduce

  1. terraform apply

Important Factoids

No response

References

No response

b/348691952

@RomeoAva RomeoAva added the bug label Jun 20, 2024
@github-actions github-actions bot added forward/review In review; remove label to forward service/bigquery labels Jun 20, 2024
@ggtisc ggtisc self-assigned this Jun 21, 2024
@ggtisc
Copy link
Collaborator

ggtisc commented Jun 21, 2024

Confirmed issue!

According to Google Cloud documentation in the bq section describes the next format for the assets param:

params='{"assets":["Account"]

But after running a terraform apply it returns the next error:

Inappropriate value for attribute "params": element "assets": string required.

@ggtisc ggtisc removed their assignment Jun 21, 2024
@ggtisc ggtisc removed the forward/review In review; remove label to forward label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants