Test standard provider with Airflow 2.8 and 2.9

[potiuk]

The standard provider has now min version of Airflow = 2.8 since #43553, but we have not tested it for Airflow 2.8 and 2.9.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

Ha.... so we are NOT good with standard provider for 2.8 and 2.9 YET

[gopidesupavan]

Ha.... so we are NOT good with standard provider for 2.8 and 2.9 YET

hm sorry my bad 😞 , i thought only on airflow 2.10

[potiuk]

Ha.... so we are NOT good with standard provider for 2.8 and 2.9 YET

hm sorry my bad 😞 , i thought only on airflow 2.10

No worries :). Nice excercise to fix it for 2.8 and 2.9 :)

[potiuk]

There are still some interesting problems to solve :). I already found another teething problem from providers move :)

[gopidesupavan]

alright got it where the failures coming from for this providers/tests/standard/operators/test_python.py::TestBranchExternalPythonOperator::test_use_airflow_context_touch_other_variables its acutally difference in the deserialisation between 2.8 and 2.10

2.10 has this casting Context: https://github.com/apache/airflow/blob/v2-10-stable/airflow/serialization/serialized_objects.py#L829, where as 2.8 and 2.9 doesn't have this implementation.

[potiuk]

alright got it where the failures coming from for this providers/tests/standard/operators/test_python.py::TestBranchExternalPythonOperator::test_use_airflow_context_touch_other_variables its acutally difference in the deserialisation between 2.8 and 2.10

Nice. Good job. So now we have to find out how this deserialization happened in 2.8/2.9 PythonVirtualenv. Let me take a look

[potiuk]

AH... Of course. Sending context was added in 3.0.0 :) . So the fact that it actually works on 2.10 is a bonus of new standard providers, but there should be no expectation it should work on 2.8 or 2.9 because it never worked there!

[gopidesupavan]

AH... Of course. Sending context was added in 3.0.0 :) . So the fact that it actually works on 2.10 is a bonus of new standard providers, but there should be no expectation it should work on 2.8 or 2.9 because it never worked there!

Yeah that's correct, should we make necessary changes to support it only for 2.10+

[gopidesupavan]

Happy to make changes, I believe only need some test fixes and use_airflow_context
Parameter checks between Versions

[potiuk]

Happy to make changes, I believe only need some test fixes and use_airflow_context Parameter checks between Versions

I am fixing it :)

[potiuk]

Actually - really the thing is that that it was only working on 2.10 when ENABLE_AIP_44 was used, so we really should only enable it only for Airlfow 3+

[gopidesupavan]

Actually - really the thing is that that it was only working on 2.10 when ENABLE_AIP_44 was used, so we really should only enable it only for Airlfow 3+

Yes your correct. for airflow less thank 3 versions we can disable, currently by default its coming as true for all the versions.

I ran this in local ,
breeze shell --use-airflow-version 2.8.4 --mount-sources providers-and-tests and in the tests its coming as true.

raised change here: #43818

[potiuk]

@gopidesupavan - you can rebase and check yout #43818 now

[gopidesupavan]

@gopidesupavan - you can rebase and check yout #43818 now

woohoo merged thank you @potiuk :) . Let me rebase other pr.

[eladkal]

This will be overridden during release time as the provider __init__ is generated from template.

[eladkal]

Raised #44017

[potiuk]

aaaaaa! !