dstandish edited a comment on pull request #15120: URL: https://github.com/apache/airflow/pull/15120#issuecomment-812579636
> By logging error, it can be helpful if the user expects to use a specific backend for the secret or fails for unexpected reasons (PermissionDenied). Yes in theory it can be helpful. BUT it can also be misleading! If a particular connection uses env vars or metastore you'll see an "error" in every log and this is misleading and confusing for users. At my company when I implemented ssm secrets backend a user saw this error and coincidentally happened to be having other problems with a dag he was working on. Not finding the cred was exactly what should have happened because the setup is supposed to use the aws instance profile not airflow connection. But they saw this "error" in the logs and it made it harder for them to find what was the actual issue because they were distracted by this "error". And they had a tough time understanding that this was fully expected and unrelated to their actual issue. So, while those of us who understand what's happening under the hood can make sense of this "error", users may not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
