-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of testing Providers that were prepared on April 25, 2023 #30849
Comments
All good for me |
I just got this issue installing in MWAA using Airflow 2.5.1:
Here is my
My constraints file is basically
And I save this as |
yes, I feel it can use cause version conflict issues if we install with Airflow version less than 2.6.0 here the version looks correct https://raw.githubusercontent.com/apache/airflow/constraints-2.6.0rc1/constraints-3.10.txt |
I'll need to talk to the MWAA team about the timeline for 2.6 and possibly issue instructions that 8.0.0 will only work with 2.6+. |
#30748 works as expected |
This is very drastic. Setting provider minimum version to 2.6 will means that all bug fixes and features would be denied from users of earlier versions. Consider many users who don't even use deferable operators... Lets wait to hear from AWS Airflow team |
Closed in favor of RC3 issue tracking |
I have a kind request for all the contributors to the latest provider packages release.
Could you please help us to test the RC versions of the providers?
Let us know in the comment, whether the issue is addressed.
Those are providers that require testing as there were some substantial changes introduced:
Provider amazon: 8.0.0rc2
DynamoDBValueSensor
(#30703): @mrichmanresource_type
orclient_type
(#30595): @utkarsharma2The guidelines on how to test providers can be found in
Verify providers by contributors
I have marked issues that were tested in RC1 as completed.
All users involved in the PRs:
@syedahsn @eladkal @utkarsharma2 @vincbeck @vandonr-amz @shahar1 @dakshin-k @mrichman @jlaneve
Committer
The text was updated successfully, but these errors were encountered: