Conversation
Google retired the "Stackdriver" brand years ago. This handler only calls the Cloud Logging API v2 (google.cloud.logging, LoggingServiceV2Client), distinct from the Cloud Monitoring API v3 that the hook, operators and links call, which were already renamed to CloudMonitoring* in a prior change. Rename this handler to match, for the same reason. StackdriverRemoteLogIO and StackdriverTaskHandler remain importable as deprecated aliases of CloudLoggingRemoteLogIO and CloudLoggingTaskHandler until March 31, 2027, per the provider's deprecation policy. The stackdriver:// remote-logging scheme is unchanged, so existing remote_base_log_folder configuration keeps working without edits. Core's airflow_local_settings.py still imports and instantiates the now-deprecated StackdriverRemoteLogIO for that scheme, so a released core paired with this provider emits one deprecation warning at startup until a follow-up core change switches to CloudLoggingRemoteLogIO. Part of the rename tracked in apache#61009.
shahar1
force-pushed
the
rename-google-stackdriver-logging
branch
from
September 22, 2026 21:39
2e4dfdc to
8645487
Compare
This branch has not been deployed
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
1 participant
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.
related: #61009
AI Summary
Renames the Google provider's task log handler from
StackdriverTaskHandler/StackdriverRemoteLogIO(moduleairflow.providers.google.cloud.log.stackdriver_task_handler) toCloudLoggingTaskHandler/CloudLoggingRemoteLogIO(moduleairflow.providers.google.cloud.log.cloud_logging_task_handler), matching the API it calls (Cloud Logging API v2). Follow-up to #73354, which renamed the Cloud Monitoring hook, operators and links.AirflowProviderDeprecationWarningon instantiation, planned removal March 31, 2027), with the same mechanics and date as Rename Google Stackdriver operators and hook to Cloud Monitoring #73354.stackdriver://remote-logging scheme is unchanged, so existingremote_base_log_foldervalues keep working.logging/cloud_logging.rstwith a redirect; the old Sphinx labels are preserved.StackdriverTaskHandler().iois now aCloudLoggingRemoteLogIO, andLOG_NAME(the UI's external log label) reads "Google Cloud Logging".airflow_local_settings.pystill instantiatesStackdriverRemoteLogIOforstackdriver://, so a released core paired with this provider logs one deprecation warning at startup until a core follow-up switches that import toCloudLoggingRemoteLogIO.Verification:
providers/google/tests/unit/google/cloud/log/(90 passed),airflow-core/tests/unit/config_templates/test_airflow_local_settings.py(24 passed), prek pre-commit and manual stages,breeze build-docs --package-filter apache-airflow-providers-google(0 warnings).Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5.1, with Sonnet 5 and Opus 5 subagents) following the guidelines