Remove airflow.utils dependency from Docker provider#69900
Open
shaealh wants to merge 1 commit into
Open
Conversation
The Docker provider should not require a core utility import for generating ephemeral service names as provider/client separation progresses in apache#62063.
SameerMesiah97
approved these changes
Jul 15, 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
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
Issue #62063 tracks removing provider dependencies on
airflow.utilsas part of the provider/client separation work. The Docker provider had one remaining dependency inDockerSwarmOperatorfor generating temporary service names.What changed
airflow.utils.strings.get_random_stringimport with a private provider-local helper.providers/docker/srcno longer importsairflow.utils.This does not introduce any user-facing behavior changes.
Testing
related: #62063