[Bug]: when adding BigQuery data source the `project` field is immutable
Describe the bug
I tried adding a BigQuery connection through the UI but couldn't type anything in the project field.
Steps to Reproduce
My package.json deps:
"dependencies": {
"@evidence-dev/bigquery": "^2.0.10",
"@evidence-dev/core-components": "^5.2.2",
"@evidence-dev/duckdb": "^1.0.13",
"@evidence-dev/evidence": "^40.1.2",
"@evidence-dev/postgres": "^1.0.7",
"@evidence-dev/source-javascript": "^0.0.3"
},
Logs
System Info
Severity
serious, but I can work around it
Additional Information, or Workarounds
Selected "serious" severity because currently docs on manual BigQuery configuration are missing.
The suggested approach is to upload a key file, which auto populates this field
What if I don't have a key file (local development with gcloud auth login)?
Also, I understand the convenience of the field being auto-populated during certain workflows, but why can't it be configured manually at the same time?
Ah yes this looks like a bug
As a workaround, you can add the files to your sources directly like:
/sources/big_query/connection.yaml
name: big_query
type: bigquery
options:
location: US
authenticator: cli
sources/big_query/connection.options.yaml
# Base64 is NOT encryption, and should not be treated as secure
project_id: <base-64ed-project-id>
and then kick it off with npm run sources
Also, I understand the convenience of the field being auto-populated during certain workflows, but why can't it be configured manually at the same time?
for most connectors you can, for bigquery we ended up removing this because the newline characters in the private key can be very tricky in form fields - it seems like we accidentally also prevented other fields from being edited at the same time
Thanks, I already figured out the correct config. Should probably add it to the docs?
We're having similar issues. Please do add it to the docs @danielgafni
@liamtabib I am not a contributor here, that would be @archiewood