bug: For GCS plugin tests, the bucket name needs to be set in file

[shubham-padia]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

GCS needs to have globally unique names, so when running tests in the GCS destination plugin, I can't run the tests on the bucket name mentioned in client_test.go.

Expected Behavior

To fix this, we should allow the bucket name to be set via a .env with the current bucket name as the default.

CloudQuery (redacted) config

Steps To Reproduce

CloudQuery (redacted) logs

CloudQuery version

Additional Context

Raised as followup to a comment raised in #17602

Pull request (optional)

• I can submit a pull request

[erezrokah]

To fix this, we should allow the bucket name to be set via a .env with the current bucket name as the default.

No need for an .env in other tests we read it using os.GetEnv, e.g.

cloudquery/plugins/destination/bigquery/client/client_test.go

Line 18 in 1ea5680

ProjectID: os.Getenv("BIGQUERY_PROJECT_ID"),