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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support mockgcp for BigQueryConnectionConnection #2315

Merged

Conversation

maqiuyujoyce
Copy link
Collaborator

@maqiuyujoyce maqiuyujoyce commented Jul 18, 2024

Change description

Support mockgcp to talk to BigQuery Connection v1 API.

Tests you have done

  • [N/A] Run make ready-pr to ensure this PR is ready for review.
  • Perform necessary E2E testing for changed resources.

E2E_KUBE_TARGET=envtest RUN_E2E=1 E2E_GCP_TARGET=mock GOLDEN_REQUEST_CHECKS=1 GOLDEN_OBJECT_CHECKS=1 go test -test.count=1 -timeout 3600s -v ./tests/e2e -run TestAllInSeries/fixtures/bigqueryconnectionconnection passed.

@justinsb
Copy link
Collaborator

Hmmm... why are the tests not running....

/ok-to-test


// The returned "name" in the response uses the project number instead of
// project ID.
obj.Name = strings.ReplaceAll(fqn, "mock-project", "${projectNumber}")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I'm not sure we always use mock-project, it's probably easier to copy the fmt.Sprintf line and adapt it

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated. Now it doesn't care what project ID it is.

@justinsb
Copy link
Collaborator

Looks great. I'm a little scared that the tests don't seem to be running though...

@maqiuyujoyce
Copy link
Collaborator Author

Looks great. I'm a little scared that the tests don't seem to be running though...

The first run of the test suite never finish for some reason: https://github.com/GoogleCloudPlatform/k8s-config-connector/actions/runs/9999441455 I tried to cancel the workflow multiple times yesterday but it didn't work. I was wondering if it is the problem of GitHub...

@justinsb
Copy link
Collaborator

Yes, looks like github actions had a whoopsie yesterday: https://www.githubstatus.com/history

Want to try rebasing and force pushing?

@maqiuyujoyce
Copy link
Collaborator Author

Will do!

@maqiuyujoyce maqiuyujoyce force-pushed the 202407-bqcc-mockgcp branch from 3852aa8 to bf146c1 Compare July 19, 2024 18:26
@justinsb
Copy link
Collaborator

Awesome - thanks @maqiuyujoyce

/approve
/lgtm

Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit cdf43aa into GoogleCloudPlatform:master Jul 19, 2024
13 checks passed
@yuwenma yuwenma added this to the 1.121 milestone Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants