Jack Wotherspoon

We should update e2e tests to be similar to AlloyDB Go Connector: https://github.com/GoogleCloudPlatform/alloydb-go-connector/blob/main/e2e_test.go#L71 This format lends itself nicely to copy/paste and can allow us to update our README with permalinks...

Consider support for @databases

1

Issue to track interest in support for [@databases](https://www.atdatabases.org/) with the Cloud SQL Node.js Connector. Upvoting this issue 👍 will help us prioritize support.

Currently we cache instance connection info by `instanceConnectionName` and error out if the iam authn flag switches between consecutive connect calls. We should update the hash key (instanceConnectionName+iam authn) for...

fix: have ssl handshake check hostname

1

For Cloud SQL we need to disable checking hostname of ssl handshake because IP address does not match SAN. However, for AlloyDB this is not the case and the IP...

In serverless environments, when the CPU is throttled, the Python Connector will sometimes fail to refresh the certificate and time out. This is a feature request to allow callers to...

New best practice for checking validity of credentials is no longer `credentials.valid` which is now deprecated (as of google-auth v2.24.0). Instead the google-auth folks recommend using [`credentials.token_state`](https://github.com/googleapis/google-auth-library-python/blob/main/google/auth/credentials.py#L100) All instances of...

Add standardized debug logging

1

Add support for optional debug logging. Presently, we want to log the following: ## Logging for refresh operations - When a refresh operation starts - Before the rate limiter is...

Failed connection calls should stop the background refresh

1

When an Admin API call fails for an instance, the connector should stop the background refresh in case the failure was caused by a unrecoverable error (instance was deleted, connection...

AlloyDB has a generated package with support for an async client. Should look at switching to use it over the `aiohttp.ClientSession` that is currently being used to hit the admin...

Investigate having `user_agent` support driver version

2

Now that we support `asyncpg` and `pg8000` we should try to add the driver being used by the connector's client to the user agent string https://github.com/GoogleCloudPlatform/alloydb-python-connector/blob/main/google/cloud/alloydb/connector/client.py#L28