Status of testing Providers that were prepared on August 11, 2023 #33305
Labels
kind:meta
High-level information important to the community
testing status
Status of testing releases
Comments
eladkal
added
kind:meta
github-actions bot
pushed a commit
to astronomer/astronomer-providers
that referenced
this issue
Aug 11, 2023
airflow-oss-bot
added a commit
to astronomer/astronomer-providers
that referenced
this issue
Aug 11, 2023
vatsrahul1001
added a commit
to astronomer/astro-sdk
that referenced
this issue
Aug 11, 2023
|
Tested with our example DAGs with the following providers without encountering issues
|
|
Checked appflow #32930 - all good 👍 |
|
Ran AWS System tests against the release candidate, all looks green: https://aws-mwaa.github.io/open-source/system-tests/version/b5a4d36383c4143f46e168b8b7a4ba2dc7c54076_8.5.1rc1.html That covers #33133 and many of the other AWS commits (but I'll let the individual authors confirm, in case they want to do any other specific testing for their changes) |
|
Thank you everyone. |
pankajkoti
added a commit
to astronomer/airflow
that referenced
this issue
Aug 16, 2023
Currently, the header of the issue template requests to test the RCs. However the guideline stating how to test those providers is placed at the bottom of the issue (appearing a bit disconnected) and might not be visible easily when have to scroll to the bottom end through the list of the Provider RCs. I think it is more evident and helpful if we advertise it at the begining. e.g. we can see here apache#33305 on how it appears currently.
potiuk
pushed a commit
that referenced
this issue
Aug 17, 2023
…33439) Currently, the header of the issue template requests to test the RCs. However the guideline stating how to test those providers is placed at the bottom of the issue (appearing a bit disconnected) and might not be visible easily when have to scroll to the bottom end through the list of the Provider RCs. I think it is more evident and helpful if we advertise it at the begining. e.g. we can see here #33305 on how it appears currently.
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this issue
Jul 18, 2024
…#33439) Currently, the header of the issue template requests to test the RCs. However the guideline stating how to test those providers is placed at the bottom of the issue (appearing a bit disconnected) and might not be visible easily when have to scroll to the bottom end through the list of the Provider RCs. I think it is more evident and helpful if we advertise it at the begining. e.g. we can see here apache/airflow#33305 on how it appears currently. GitOrigin-RevId: 8b7e0babe1c3e9bef6e934d1e362564bc73fda4d
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this issue
Sep 19, 2024
…#33439) Currently, the header of the issue template requests to test the RCs. However the guideline stating how to test those providers is placed at the bottom of the issue (appearing a bit disconnected) and might not be visible easily when have to scroll to the bottom end through the list of the Provider RCs. I think it is more evident and helpful if we advertise it at the begining. e.g. we can see here apache/airflow#33305 on how it appears currently. GitOrigin-RevId: 8b7e0babe1c3e9bef6e934d1e362564bc73fda4d
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this issue
Nov 8, 2024
…#33439) Currently, the header of the issue template requests to test the RCs. However the guideline stating how to test those providers is placed at the bottom of the issue (appearing a bit disconnected) and might not be visible easily when have to scroll to the bottom end through the list of the Provider RCs. I think it is more evident and helpful if we advertise it at the begining. e.g. we can see here apache/airflow#33305 on how it appears currently. GitOrigin-RevId: 8b7e0babe1c3e9bef6e934d1e362564bc73fda4d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Body
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 alibaba: 2.5.1rc1
Provider amazon: 8.5.1rc1
template_fieldsofEcsDeregisterTaskDefinitionOperator(#33129): @eladkalProvider apache.beam: 5.2.1rc1
BeamRunPythonPipelineOperator(#31645): @yupbankProvider apache.druid: 3.5.0rc1
Provider celery: 3.3.2rc1
Provider cncf.kubernetes: 7.4.2rc1
OnFinishActionenum inherit from str to support passing it toKubernetesPodOperatpor(#33228): @raphaelauvProvider common.sql: 1.7.0rc1
Provider databricks: 4.3.3rc1
Provider docker: 3.7.3rc1
Provider exasol: 4.2.3rc1
Provider microsoft.azure: 6.2.4rc1
Provider qubole: 3.4.2rc1
Provider snowflake: 4.4.2rc1
The guidelines on how to test providers can be found in
Verify providers by contributors
All users involved in the PRs:
@eladkal @o-nikolas @potiuk @hussein-awala @eumiro @syedahsn @yupbank @vioao @raphaelauv @mahammi @vincbeck
Committer
The text was updated successfully, but these errors were encountered: