-
Notifications
You must be signed in to change notification settings - Fork 292
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
feat: Spring Cloud AlloyDB integration #2787
feat: Spring Cloud AlloyDB integration #2787
Conversation
@meltsufin This PR is ready for review. For the integration tests, we need to create a AlloyDB cluster and instance right? Can you create them? |
Was |
It was. I will remove it. |
spring-cloud-gcp-samples/spring-cloud-gcp-alloydb-sample/README.adoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Burke Davison <40617934+burkedavison@users.noreply.github.com>
|
||
You will create a cluster and primary instance, a database within the instance, populate the database and then query it. | ||
|
||
== Setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to get the sample working, but connection gave me a bit of struggle. @ttosta-google helped me understand that I either needed to run the sample from a VM within my created VPC, or enable the AlloyDB instance's for external connections.
Could there be a small section in this setup describing this expectation, and perhaps linking to https://cloud.google.com/alloydb/docs/connect-external or perhaps using the "Quickstart: Connect from Cloud Run" as the linked Quickstart instead of "Quickstart: Create and connect to a database"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. I will add a new section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added.
@meltsufin : Is there a way to force the integration tests to run, given that this PR is being opened from a forked repo? Otherwise, @ttosta-google we may need you to direct this PR to a new branch in this repo, then create a PR from that branch to main so we can trigger the ITs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor improvements + needing to figure out how to run the ITs.
Co-authored-by: Burke Davison <40617934+burkedavison@users.noreply.github.com>
Quality Gate passedIssues Measures |
e5d2557
into
GoogleCloudPlatform:feat-alloydb-integration
New PR will be opened from feat-alloydb-integration to main to allow the ITs to run. |
This PR adds a component to allow our customers to connect to Google Cloud AlloyDB instances using Spring Boot with the Java Connector integration.
It includes a starter, autoconfigure, sample, associated integrations tests and documentation.
Issue related: GoogleCloudPlatform/alloydb-java-connector#151