Switches to latest version of snowflake connector

[potiuk]

This should allow us to release a new version of snowflake
provider that is not interacting with other providers via
monkeypatching of SSL classes.

Fixes #12881

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[feluelle]

Nice!

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest master at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[github-actions]

The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Backport packages$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*.

[potiuk]

@kaxil @ashb @mik-laj @ephraimbuddy @turbaszek - when fixing the 'azure-storage' problems connected (they will be finaly solved in #12188 which I rebased on top of this one) I also simplified upgrades of setup.py so they will also automatically work in case any change in setup.py results in REMOVING dependency (as is in the case of azure-storage).

Basically - no more EPOCH changes are needed when you remove dependencies. Whenever setup.py/setup.cfg is changed all installation will skip automatically (on CI) the "cache" build and it will install everything from the scratch - that will take much longer than usual (3-4 minutes) but it should handle every case - including the removal.

I did it as part of the 'snowflake' fix because also here I want to reinstall dependencies from scratch.

[kaxil]

This will default to True right? So will use cache and L329 will take care of installing it if setup.py or setup.cfg changes?

[potiuk]

UPGRADE_TO_NEWER_DEPENDENCIES is "false" by default.

It is set in the 'selective_checks" in CI to "true" (as of few days) whenever setup.py or setup.cfg changes (

airflow/scripts/ci/selective_ci_checks.sh

Line 325 in e4b8ee6

upgrade_to_newer_dependencies="${INCOMING_COMMIT_SHA}"

)

This means that in CI, by default the "install_airflow_from_latest_master.sh" is used (and airflow is installed from cache first).

When either of the two setup files change, UPGRADE_TO_LATEST_DEPENDENCIES is set and this line is skipped, so no preinstalled packages - they are all installed from scratch (which will take a bit longer but it is 'clean' state - so anything that disappears (comparing to master) is not installed.

The situation is different when you build image locally - when you change setup.py, setup.cfg and build the image. the cache is still used (UPGRADE_TO_NEWER_DEPENDENCIES) is "false").

This way you avoid rebuilding all of the dependencies when you add new dependency (it takes ~ 10 minutes) to install all deps from the scratch.

You can still trigger the same behavior as in CI by adding --upgrade-to-newer-dependencies flag in breeze when building the image (it simply sets UPGRADE_TO_NEWER_DEPENDENCIES).

However, good that I explained it - I just realised that the comparision should be == "false" because we are using commit_hash as the "truthy" value in selective checks! Fixing it.

[github-actions]

The Workflow run is cancelling this PR. Building images for the PR has failed. Follow the the workflow link to check the reason.

[github-actions]

The Workflow run is cancelling this PR. Building images for the PR has failed. Follow the the workflow link to check the reason.

[potiuk]

Random test failure only. Merging!

[kaxil]

Should this go on 2.0.1 @potiuk ?

[potiuk]

Absolutely!