Move FAB related configs to FAB provider #49017
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vincbeck
requested review from
ephraimbuddy,
pierrejeambrun and
rawwar
as code owners
boring-cyborg
bot
added
area:API
vincbeck
commented
Apr 9, 2025
vincbeck
force-pushed
the
vincbeck/fab_config
branch
2 times, most recently
from
defe33f to
9474858
Compare
potiuk
reviewed
Apr 9, 2025
vincbeck
force-pushed
the
vincbeck/fab_config
branch
6 times, most recently
from
b3a54f3 to
790f643
Compare
potiuk
approved these changes
Apr 9, 2025
vincbeck
force-pushed
the
vincbeck/fab_config
branch
from
790f643 to
8a8cf08
Compare
vincbeck
force-pushed
the
vincbeck/fab_config
branch
from
8a8cf08 to
4259498
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move some FAB related configurations from core Airflow to FAB 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 airflow-core/newsfragments.