-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Remove incorrect deprecation warning in secrets backend #22326
Remove incorrect deprecation warning in secrets backend #22326
Conversation
When the no value is found with `get_conn_value`, the warning was being triggered, even though `get_conn_value` was implemented and just returned no value (cus there wasn't one). Now we make the logic a little tighter and only raise the dep warning when `get_conn_value` not implemented, which is what we intended to do in the first place.
I still get the warnings for the example in #19857 (comment)
|
Seems maybe you are using an external secrets backend? I cannot repro. We still need to update other secrets backends. But this fixes the issue where it yes get_conn_value is implemented but just the requested conn isn't there. |
Using breeze |
ok will take a look |
i ran in breeze... cannot repro. maybe you are on wrong branch or something?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This must have been something on my env then. It works when I try from python shell.
Logic looks good to me.
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
When the no value is found with
get_conn_value
, the warning was being triggered, even thoughget_conn_value
was implemented and just returned no value (cus there wasn't one).Now we make the logic a little tighter and only raise the dep warning when
get_conn_value
not implemented, which is what we intended to do in the first place.