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

DbAPiHook: Don't log a warning message if placeholder is None and make sure warning message is formatted correctly #39690

Merged
merged 8 commits into from
May 18, 2024

Conversation

dabla
Copy link
Contributor

@dabla dabla commented May 17, 2024

closes: #39678

This PR fixes an invalid warning message being logged when placeholder is None (and thus not defined in the connection extra field) and also makes sure that when the placeholder isn't valid, a correct warning message is being logged.


^ 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.

… if the placeholder is invalid that the warning message is logged correctly
@dabla dabla changed the title DbAPiHook: Don't log a warning message if placeholder is None and make sure warning message is correct if invalid DbAPiHook: Don't log a warning message if placeholder is None and make sure warning message is formatted correctly May 17, 2024
@Taragolis Taragolis merged commit db80e5e into apache:main May 18, 2024
41 checks passed
romsharon98 pushed a commit to romsharon98/airflow that referenced this pull request Jul 26, 2024
…e sure warning message is formatted correctly (apache#39690)

* fix: Don't log a warning message if placeholder is None and make sure if the placeholder is invalid that the warning message is logged correctly

* refactor: Also make sure to verify that log.warning isn't invoked when placeholder is valid

* refactor: All assertions regarding the logging are now done through caplog

* refactor: Reformatted logging assertions

* refactor: Reformatted logging assertion

---------

Co-authored-by: David Blain <david.blain@infrabel.be>
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.

GenericTransfer - Warning: "Placeholder defined in Connection..."
4 participants