Skip to content
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

Move triggers and remaining operators/sensors into standard provider #43571

Conversation

gopidesupavan
Copy link
Member

Moving core area triggers and remaining operators/sensors inside 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.rst or {issue_number}.significant.rst, in newsfragments.

@@ -73,7 +73,7 @@

from airflow import settings, utils
from airflow.api_internal.internal_api_call import internal_api_call
from airflow.assets import Asset, AssetAlias, BaseAsset
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why we removed it here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it removed by mistake when moving and import resolution, will update. :)

@@ -846,6 +846,7 @@
"plugins": [],
"cross-providers-deps": [
"amazon",
"common.compat",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why we need this change here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are using compat provider for imports to work with old core location. so here in this case msgraph uses timedelta, https://github.com/apache/airflow/pull/43571/files/a750af6fec2a04ba5a347303fb4397a4e496d56e#diff-af3b61e0f2e76a9841ce87162351100deee4bc736a90d4cb8715acd9fb61473cR23

pre-commit generated this with common.compat as cross provider

@gopidesupavan
Copy link
Member Author

Does email operator/email utils is required to move inside standard provider?

@gopidesupavan
Copy link
Member Author

This pr getting more and more changes i feel and some changes require in selective checks to remove OPERATORS tests from core area. So i feel better to have split the triggers to separate pr #43608.

Will update this later.

@potiuk
Copy link
Member

potiuk commented Nov 2, 2024

This pr getting more and more changes i feel and some changes require in selective checks to remove OPERATORS tests from core area. So i feel better to have split the triggers to separate pr #43608.

Will update this later.

Makes sense

@eladkal
Copy link
Contributor

eladkal commented Dec 1, 2024

Do we still need this PR or was it break into smaller ones that were already merged?

@gopidesupavan
Copy link
Member Author

Do we still need this PR or was it break into smaller ones that were already merged?

Don't think this is required, kept open to double check the final checks. I think we are good I will close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants