GCP Secret Manager Error Handling for Missings Credentials

[fhoda]

related: #16404

Split of the above referenced PR (secrets backend failover). See #16404 (comment)

This one just has the GCP Secret Manager error handling.

[uranusjr]

I wonder if it’d be a good idea to list the paths and check if GOOGLE_APPLICATION_CREDENTIALS is set (probably not a good idea to show its value). That’d make debugging much easier.

[kaxil]

The log.exception will probably show that error as that is raised from/by get_credentials_and_project_id I think

airflow/airflow/providers/google/cloud/utils/credentials_provider.py

Line 225 in 866a601

def get_credentials_and_project(self) -> Tuple[google.auth.credentials.Credentials, str]:

airflow/airflow/providers/google/cloud/utils/credentials_provider.py

Lines 287 to 288 in 866a601

	self._log_info(
	'Getting connection using `google.auth.default()` since no key file is defined for hook.'

airflow/airflow/providers/google/cloud/utils/credentials_provider.py

Lines 276 to 278 in 866a601

	if not self.key_path.endswith('.json'):
	raise AirflowException('Unrecognised extension for key file.')

[uranusjr]

Yes, but I was thinking it’d use useful to know what the value of self.key_path is in the above context, so I don’t need to hunt the value in my configs. But maybe google-auth already includes that in the exception, no idea.

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.