Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 13 commits
- 62 files changed
- 3 contributors
Commits on Apr 16, 2025
Commits on Apr 18, 2025
Commits on Apr 25, 2025
-
chore: shorten duration of connector unit tests (#444)
test_connector.py and test_async_connector.py were taking around a minute to run. The reason for this is that the AlloyDB Admin API client sets a default deadline of 60s to retry failed API requests. This increases the time for certain unit tests, which send actual API requests. This PR overrides the timeout to 1s for those unit tests, to speed up their execution.
Commits on Apr 28, 2025
Commits on Apr 29, 2025
-
fix: support verify-full mode (#446)
This PR allows the Python connector to support the most secure form of mTLS, which is `verify-full` mode: https://www.postgresql.org/docs/current/libpq-ssl.html#LIBQ-SSL-CERTIFICATES. In `verify-full` mode, the hostname provided by the client is matched with the AuthProxy server's certificate's SAN field. If it does not match, the connection is rejected. Previously, for PSC instances, the AuthProxy server certificates contained DNS names with trailing dots in the SAN field. But Python's OpenSSL library does not allow DNS names to contain trailing dots when doing the hostname verification. So we could not support `verify-full` mode. As of now, all PSC instances that use the AlloyDB Python connector do not have DNS names with trailing dots in the SAN field anymore. So we can support `verify-full` mode now.
-
build: remove .kokoro folder (#447)
This is the AlloyDB version of GoogleCloudPlatform/cloud-sql-python-connector#1237.
Commits on May 9, 2025
-
feat: create alias alloydbconnector package (#451)
This PR creates a new package: google.cloud.alloydbconnector, which is an alias to google.cloud.alloydb.connector. The implementation resides in google.cloud.alloydbconnector, and google.cloud.alloydb.connector points to it. So importing google.cloud.alloydbconnector is the same as importing google.cloud.alloydb.connector. This PR aims to fix googleapis/google-cloud-python#13871, where a PEX environment, containing google-cloud-alloydb and alloydb-python-connector packages, fails to import google.cloud.alloydb.connector, because it attempts to find a connector/ directory under the google-cloud-alloydb package, which does not exist. The fix is that the user should import the google.cloud.alloydbconnector package instead. This PR also updates the README and integration tests to mention importing google.cloud.alloydbconnector instead of google.cloud.alloydb.connector. This serves as documentation so that new users of the library will instead import google.cloud.alloydbconnector. Existing users can continue to import google.cloud.alloydb.connector without any issues.
Commits on May 13, 2025
-
-
chore(deps): update python-nonmajor (#439)
* chore(deps): update python-nonmajor * Update requirements-test.txt --------- Co-authored-by: rhatgadkar-goog <rhatgadkar@google.com>
-
chore(main): release 1.9.0 (#437)
* chore(main): release 1.9.0 * Update CHANGELOG.md --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: rhatgadkar-goog <rhatgadkar@google.com>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.8.0...v1.9.0