HASURA_BIGQUERY_DATASET_ID is not properly used

[scarter93]

Summary

HASURA_BIGQUERY_DATASET_ID seems to be ignored during build/runtime — schemaName in configuration.json appears to be what is actually used.

Steps to Reproduce

1. Initialize a native BigQuery connector:

   ddn connector init bigquery

2. Introspect:

   ddn connector introspect

3. Inspect configuration.json and note hardcoded dataset on each table, e.g.:

   "schemaName": "my_project.my_dataset"

4. Create/Switch context with a different dataset (e.g., my_dataset_prod) and rebuild without re-introspection.
5. Execute queries -> they still hit my_dataset due to the static schemaName.

Impact

• Multi-environment (dev/prod) pipelines cannot reuse the same connector config.
• Requires either re-introspection per environment or manual JSON rewriting.
• My understanding is the expectation that connection settings are fully environment-driven per: https://hasura.io/docs/3.0/project-configuration/project-management/manage-environments

Proposed Fix

Use environment variables as expected at build or runtime.

[scarter93]

any updates?