Add S3RemoteLogIO.from_config and register s3 remote logging scheme#69817
Merged
jason810496 merged 1 commit intoJul 22, 2026
Merged
Conversation
1 task
jason810496
force-pushed
the
feature/logging/s3-remote-log-io-from-config
branch
2 times, most recently
from
July 18, 2026 13:12
bb01bb5 to
a09a4ab
Compare
jason810496
marked this pull request as ready for review
July 18, 2026 13:12
jason810496
commented
Jul 18, 2026
jason810496
left a comment
jason810496
left a comment
Member
Author
There was a problem hiding this comment.
Here're more context about the changes itself.
ferruzzi
reviewed
Jul 20, 2026
Member
Author
|
Thanks for the review! |
Airflow resolves remote task log handlers through provider dispatch on the remote_base_log_folder URL scheme since apache#67056; providers must expose from_config so core and the Task SDK no longer depend on the hardcoded branches in airflow_local_settings.py. This migrates the s3 scheme as the first adopter.
jason810496
force-pushed
the
feature/logging/s3-remote-log-io-from-config
branch
from
July 22, 2026 03:01
a09a4ab to
24663d6
Compare
This was referenced Jul 23, 2026
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
2 participants
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.
Why
#67056 decoupled remote logging from the hardcoded branches in
airflow_local_settings.py: core and the Task SDK now resolve the handler via ProvidersManager dispatch on the[logging] remote_base_log_folderURL scheme, instantiating the provider class through a no-argfrom_config()classmethod. This migrates thes3scheme as the first adopter.What
S3RemoteLogIO.from_config(), mirroring the legacyairflow_local_settings.pybranch -- including the[logging] remote_task_handler_kwargsIO-kwargs merge andexpanduseronbase_log_folder, so behavior is unchanged for existing configs.s3scheme in the amazonget_provider_info.py.Note
A sibling PR migrates the
cloudwatchscheme the same way (#69816); whichever merges second needs a trivial rebase of the newremote-logging:section. Iffrom_configraises on a bad config, the shared factory falls back to the legacy path, so this is not a breaking change.Was generative AI tooling used to co-author this PR?