Don't consider airflow core conf for KPO#26849
Merged
dstandish merged 3 commits intoapache:mainfrom Oct 4, 2022
Merged
Conversation
boring-cyborg
bot
added
provider:cncf-kubernetes
jedcunningham
approved these changes
Oct 3, 2022
potiuk
approved these changes
Oct 3, 2022
eladkal
approved these changes
Oct 3, 2022
Member
|
Test is failing |
dstandish
force-pushed
the
remove-kpo-consideration-core-params
branch
from
a87ddfe to
67ad563
Compare
This was deprecated in provider version 4.1.0, and now we are removing the backcompat logic, so that core conf params will no longer be considered when creating the k8s client object; users will need to use Airflow connections if they want the client configured in a non-default way.
dstandish
force-pushed
the
remove-kpo-consideration-core-params
branch
from
67ad563 to
bfda3a3
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Note: this should not be released until provider version 5.0
This was deprecated in provider version 4.1.0, and now we are removing the backcompat logic, so that core conf params will no longer be considered when creating the k8s client object; users will need to use Airflow connections if they want the client configured in a non-default way.