Standard provider bash operator#42252
Conversation
3ae4647 to
a870160
Compare
|
moving this bash operator to standard provider, has module path changes in systems test, integration tests. failures in python client tests, i am thinking due to bashoperator path change, causing dag not loaded. |
0ead57d to
c5f4c04
Compare
|
Could you please help on this, kubernetes executor tests are failing with dag not found |
|
After reviewing the logs, it seems the reason the k8s tests are failing is due to the absence of the standard provider package in the image. This is because i guess the standard provider not included in the prod_image_installed_providers.txt file ? Is it okay to add standard provider in to that file? |
50525db to
9905f25
Compare
7745a13 to
726518b
Compare
There is a test failing , but its not related to this. Would you be able to merge please? |
Standard provider should be added to chicken-egg-providers as it has not yet been officially released, so we need to add it. This can only be done via "apache" PR as it is needed in build-images workflow. This is needed to unblock apache#42252
Standard provider should be added to chicken-egg-providers as it has not yet been officially released, so we need to add it. This can only be done via "apache" PR as it is needed in build-images workflow. This is needed to unblock apache#42252
Standard provider should be added to chicken-egg-providers as it has not yet been officially released, so we need to add it. This can only be done via "apache" PR as it is needed in build-images workflow. This is needed to unblock apache#42252
Standard provider should be added to chicken-egg-providers as it has not yet been officially released, so we need to add it. This can only be done via "apache" PR as it is needed in build-images workflow. This is needed to unblock apache#42252


Moving bash operators/sensors to standard provider
^ 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.rstor{issue_number}.significant.rst, in newsfragments.