concourse / concourse/docker-image-resource
Docker image tag `get` stage override
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
Is it possible to add support for the subject feature?
Right now an image's tag can be supplied for the source only, i.e. once for the whole pipeline:
- name: my_image
type: docker-image
icon: docker
source:
repository: <some registry>
tag: X.Y.Z
<<: *repository_credentials
The idea (and necessity) to have it overridden per task, e.g. per environment used (dev / stage / prod):
- name: build-dev
plan:
- get: my_image
params:
save: true
tag: "X.Y.Z+1" # tag override here
as a bonus, with such override it can be dynamic via load_vars step from a shared config source.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the resource's handling of the Concourse get step and its parameters, then trace how the Docker image tag is selected. Check existing tests for get behavior and add coverage showing that a task-level tag overrides the source tag, including the requested dynamic value path. Done means per-task overrides work without changing the source default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100