feat: support container image fallback lists#698
Draft
claymcleod wants to merge 2 commits intomainfrom
Draft
Conversation
When a WDL task specifies an array of container images in its `container` requirement, each candidate is now tried in order until one pulls successfully. The wildcard value `*` resolves to the configured default container at parse time. Closes #691
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.
When a WDL task specifies an array of container images in its
containerrequirement, each candidate is now tried in order until one pulls successfully. This lets task authors provide fallback images for environments where a preferred registry might not be reachable. The WDL wildcard value*resolves to the configured default container (e.g.,ubuntu:latest) at parse time rather than being modeled as a separate enum variant.The actual container that was used during execution is now tracked via
TaskExecutionResultand stored inTaskPostEvaluationData, so downstream consumers always know which image ran—not just which candidates were offered.Closes #691
Before submitting this PR, please make sure:
For all contributors:
nextbranch in the sprocket.bio repository (when appropriate).