From a35a1c9ab5c6f3368cc53343d50f80e9337fc166 Mon Sep 17 00:00:00 2001 From: ckunki Date: Thu, 11 Dec 2025 08:28:26 +0100 Subject: [PATCH 1/3] Forced validation of SaaS SSL certificates --- test/integration/connection_test.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/integration/connection_test.py b/test/integration/connection_test.py index 4cbcb53..e55cf84 100644 --- a/test/integration/connection_test.py +++ b/test/integration/connection_test.py @@ -6,7 +6,7 @@ from exasol.saas.client.api_access import get_connection_params -SSL_OPTIONS = {"websocket_sslopt": {"cert_reqs": ssl.CERT_NONE}} +SSL_OPTIONS = {"websocket_sslopt": {"cert_reqs": ssl.CERT_REQUIRED}} @pytest.fixture From 10a9a45e935a79008c55ee1f5ddc4a5849f6fe3a Mon Sep 17 00:00:00 2001 From: ckunki Date: Thu, 11 Dec 2025 09:21:15 +0100 Subject: [PATCH 2/3] Updated changelog --- doc/changes/changes_2.6.0.md | 2 +- doc/changes/unreleased.md | 8 ++++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/changes/changes_2.6.0.md b/doc/changes/changes_2.6.0.md index dbc5013..3625cc9 100644 --- a/doc/changes/changes_2.6.0.md +++ b/doc/changes/changes_2.6.0.md @@ -4,7 +4,7 @@ This release changes the strategy for deleting a SaaS database instance, as required by the changed behavior of the actual SaaS backend. -Before, SAPIPY used only a fixed waiting time. In case of HTTP responses with status code 400 and message `Operation.*not allowed.*cluster.*not.*in.*proper state` SAPIPY now retries deleting the SaaS instance for max. 5 minutes. +Before, SAPIPY used only a fixed waiting time. In case of HTTP responses with status code 400 and their message containing "cluster is not in a proper state" SAPIPY now retries deleting the SaaS instance for max. 30 minutes. ## Bugfixes diff --git a/doc/changes/unreleased.md b/doc/changes/unreleased.md index 79e701b..8e31d73 100644 --- a/doc/changes/unreleased.md +++ b/doc/changes/unreleased.md @@ -1 +1,9 @@ # Unreleased + +## Summary + +tbd. + +## Refactorings + +* #128: Explicitly configured validation of SaaS SSL certificates in pyexasol connection From ea93bbe4f53e4d3d144d2e3f3beb60d57238afe2 Mon Sep 17 00:00:00 2001 From: Christoph Kuhnke Date: Thu, 11 Dec 2025 09:56:03 +0100 Subject: [PATCH 3/3] Update doc/changes/changes_2.6.0.md Co-authored-by: Mikhail Beck --- doc/changes/changes_2.6.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/changes/changes_2.6.0.md b/doc/changes/changes_2.6.0.md index 3625cc9..ec0282d 100644 --- a/doc/changes/changes_2.6.0.md +++ b/doc/changes/changes_2.6.0.md @@ -4,7 +4,7 @@ This release changes the strategy for deleting a SaaS database instance, as required by the changed behavior of the actual SaaS backend. -Before, SAPIPY used only a fixed waiting time. In case of HTTP responses with status code 400 and their message containing "cluster is not in a proper state" SAPIPY now retries deleting the SaaS instance for max. 30 minutes. +Before, SAPIPY used only a fixed waiting time. In case of HTTP responses with status code 400 and their messages containing the text "cluster is not in a proper state" SAPIPY now retries deleting the SaaS instance for max. 30 minutes. ## Bugfixes