cloud-sql-python-connector 1.18.4__tar.gz → 1.19.0__tar.gz

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cloud-sql-python-connector
-Version: 1.18.4
+Version: 1.19.0
 Summary: Google Cloud SQL Python Connector library
 Author-email: Google LLC <googleapis-packages@google.com>
 License-Expression: Apache-2.0
@@ -387,14 +387,27 @@ conn = connector.connect(
 )
 ```
 
-### Using DNS domain names to identify instances
+### Using Advanced Disaster Recovery and DNS domain names to identify instances
 
-The connector can be configured to use DNS to look up an instance. This would
-allow you to configure your application to connect to a database instance, and
-centrally configure which instance in your DNS zone.
+The connector can be configured to use DNS to look up an instance. 
+Use a DNS name managed by Cloud SQL [Advanced Disaster Recovery](https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery), 
+or a domain name that you manage.
+
+#### Using Advanced Recovery Write Endpoint DNS Name
+
+[Advanced Disaster Recovery](https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery)
+creates geographically distributed replicas of your Cloud SQL database instance. When you perform 
+switchover or failover on the database instance, the connector will gracefully disconnect from the
+old primary instance and reconnect to the new primary instance. 
+
+Follow the instructions in [Connect using Write Endpoint](https://docs.cloud.google.com/sql/docs/mysql/connect-to-instance-using-write-endpoint)
+to get the write endpoint DNS name for your primary instance. Then, use this write endpoint DNS
+name to configure the connector.
 
 #### Configure your DNS Records
 
+The connector may be configured to use DNS that you define as well.
+
 Add a DNS TXT record for the Cloud SQL instance to a **private** DNS server
 or a private Google Cloud DNS Zone used by your application.
 
@@ -605,7 +618,7 @@ from google.cloud.sql.connector import Connector, create_async_connector
 
 async def main():
     # initialize Connector object for connections to Cloud SQL
-    connector = create_async_connector()
+    connector = await create_async_connector()
 
     # creation function to generate asyncpg connections as the 'connect' arg
     async def getconn(instance_connection_name, **kwargs) -> asyncpg.Connection:

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/README.md

@@ -348,14 +348,27 @@ conn = connector.connect(
 )
 ```
 
-### Using DNS domain names to identify instances
+### Using Advanced Disaster Recovery and DNS domain names to identify instances
 
-The connector can be configured to use DNS to look up an instance. This would
-allow you to configure your application to connect to a database instance, and
-centrally configure which instance in your DNS zone.
+The connector can be configured to use DNS to look up an instance. 
+Use a DNS name managed by Cloud SQL [Advanced Disaster Recovery](https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery), 
+or a domain name that you manage.
+
+#### Using Advanced Recovery Write Endpoint DNS Name
+
+[Advanced Disaster Recovery](https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery)
+creates geographically distributed replicas of your Cloud SQL database instance. When you perform 
+switchover or failover on the database instance, the connector will gracefully disconnect from the
+old primary instance and reconnect to the new primary instance. 
+
+Follow the instructions in [Connect using Write Endpoint](https://docs.cloud.google.com/sql/docs/mysql/connect-to-instance-using-write-endpoint)
+to get the write endpoint DNS name for your primary instance. Then, use this write endpoint DNS
+name to configure the connector.
 
 #### Configure your DNS Records
 
+The connector may be configured to use DNS that you define as well.
+
 Add a DNS TXT record for the Cloud SQL instance to a **private** DNS server
 or a private Google Cloud DNS Zone used by your application.
 
@@ -566,7 +579,7 @@ from google.cloud.sql.connector import Connector, create_async_connector
 
 async def main():
     # initialize Connector object for connections to Cloud SQL
-    connector = create_async_connector()
+    connector = await create_async_connector()
 
     # creation function to generate asyncpg connections as the 'connect' arg
     async def getconn(instance_connection_name, **kwargs) -> asyncpg.Connection:

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/cloud_sql_python_connector.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cloud-sql-python-connector
-Version: 1.18.4
+Version: 1.19.0
 Summary: Google Cloud SQL Python Connector library
 Author-email: Google LLC <googleapis-packages@google.com>
 License-Expression: Apache-2.0
@@ -387,14 +387,27 @@ conn = connector.connect(
 )
 ```
 
-### Using DNS domain names to identify instances
+### Using Advanced Disaster Recovery and DNS domain names to identify instances
 
-The connector can be configured to use DNS to look up an instance. This would
-allow you to configure your application to connect to a database instance, and
-centrally configure which instance in your DNS zone.
+The connector can be configured to use DNS to look up an instance. 
+Use a DNS name managed by Cloud SQL [Advanced Disaster Recovery](https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery), 
+or a domain name that you manage.
+
+#### Using Advanced Recovery Write Endpoint DNS Name
+
+[Advanced Disaster Recovery](https://docs.cloud.google.com/sql/docs/mysql/use-advanced-disaster-recovery)
+creates geographically distributed replicas of your Cloud SQL database instance. When you perform 
+switchover or failover on the database instance, the connector will gracefully disconnect from the
+old primary instance and reconnect to the new primary instance. 
+
+Follow the instructions in [Connect using Write Endpoint](https://docs.cloud.google.com/sql/docs/mysql/connect-to-instance-using-write-endpoint)
+to get the write endpoint DNS name for your primary instance. Then, use this write endpoint DNS
+name to configure the connector.
 
 #### Configure your DNS Records
 
+The connector may be configured to use DNS that you define as well.
+
 Add a DNS TXT record for the Cloud SQL instance to a **private** DNS server
 or a private Google Cloud DNS Zone used by your application.
 
@@ -605,7 +618,7 @@ from google.cloud.sql.connector import Connector, create_async_connector
 
 async def main():
     # initialize Connector object for connections to Cloud SQL
-    connector = create_async_connector()
+    connector = await create_async_connector()
 
     # creation function to generate asyncpg connections as the 'connect' arg
     async def getconn(instance_connection_name, **kwargs) -> asyncpg.Connection:

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/google/cloud/sql/connector/connector.py

@@ -28,11 +28,13 @@ from typing import Any, Callable, Optional, Union
 import google.auth
 from google.auth.credentials import Credentials
 from google.auth.credentials import with_scopes_if_required
+
 import google.cloud.sql.connector.asyncpg as asyncpg
 from google.cloud.sql.connector.client import CloudSQLClient
 from google.cloud.sql.connector.enums import DriverMapping
 from google.cloud.sql.connector.enums import IPTypes
 from google.cloud.sql.connector.enums import RefreshStrategy
+from google.cloud.sql.connector.exceptions import ConnectorLoopError
 from google.cloud.sql.connector.instance import RefreshAheadCache
 from google.cloud.sql.connector.lazy import LazyRefreshCache
 from google.cloud.sql.connector.monitored_cache import MonitoredCache
@@ -280,6 +282,15 @@ class Connector:
             KeyError: Unsupported database driver Must be one of pymysql, asyncpg,
                 pg8000, and pytds.
         """
+        # check if event loop is running in current thread
+        if self._loop != asyncio.get_running_loop():
+            raise ConnectorLoopError(
+                "Running event loop does not match 'connector._loop'. "
+                "Connector.connect_async() must be called from the event loop "
+                "the Connector was initialized with. If you need to connect "
+                "across event loops, please use a new Connector object."
+            )
+
         if self._keys is None:
             self._keys = asyncio.create_task(generate_keys())
         if self._client is None:

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/google/cloud/sql/connector/refresh_utils.py

@@ -24,7 +24,6 @@ import random
 from typing import Any, Callable
 
 import aiohttp
-
 from google.auth.credentials import Credentials
 from google.auth.credentials import Scoped
 import google.auth.transport.requests

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/google/cloud/sql/connector/version.py

@@ -12,4 +12,4 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-__version__ = "1.18.4"
+__version__ = "1.19.0"

{cloud_sql_python_connector-1.18.4 → cloud_sql_python_connector-1.19.0}/google/cloud/sql/connector/client.py

@@ -22,9 +22,9 @@ from typing import Any, Optional, TYPE_CHECKING
 import aiohttp
 from cryptography.hazmat.backends import default_backend
 from cryptography.x509 import load_pem_x509_certificate
-
 from google.auth.credentials import TokenState
 from google.auth.transport import requests
+
 from google.cloud.sql.connector.connection_info import ConnectionInfo
 from google.cloud.sql.connector.connection_name import ConnectionName
 from google.cloud.sql.connector.exceptions import AutoIAMAuthNotSupported