deploy-testlists.yml does not update container with tag latest if it is already running
Open
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 4
- Forks
- 15
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 4
Description
when deploying this service, if the container is already running, it does not get redeployed.
workaround: deploy a specific tag-by-hash to ensure the correct container is running/deployed.
there is probably another way to ensure that the container is redeployed when the playbook is run.
Contributor guide
No contributing guide indexed for this repository
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 inspecting deploy-testlists.yml and run the playbook with a service container already running with the latest tag. Trace how the playbook decides whether the container needs deployment, then verify that rerunning it replaces an outdated running container with the current latest image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100