Update requirements to allow OpenSSL 3.0 usage #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
N.B. With this PR to
CBRO-1218-undo-migrations
we diverge one more version from the original schemachange.Original schemachange didn't have any meaninful for us changes since 3.5.2. Changelog.
Swithing to Debian 12 in python base image caused OpenSSL switch from 1.1.1 to 3.0.
Current version of
snowflake-connector-python
2.8.0 which depends onpyopenssl
22.1.0 fails because of OpenSSL switch.Failed pipeline: https://ci.at.samo.io/job/salemove/job/snowflake-ingestion/job/PR-589/8/consoleFull
After the update of
snowflake-connector-python
to 3.7.0pyopenssl
becomes
23.3.0
and doesn't fail anymore in this image.Tested
snowflake-ingestion
in this PR with base image update.Pipeline doesn't fail anymore, and does migration/rollback successfully.
CBRO-1908