-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker_tag
does not detect changes when the docker_image
referenced by source_image
changes
#567
Comments
Would be very nice to add a |
@labmonkey42 I fully agree that it would be nice for the In the meantime, I managed to implement a workaround using Terraform's replace_triggered_by. If you're on Terraform
Hope this helps! |
Community Note
Terraform (and docker Provider) Version
1.3.9
Affected Resource(s)
docker_tag
Terraform Configuration Files
Expected Behaviour
Any change to the upstream image at
registry1.example.org/ns/foo:latest
should ultimately result in a copy atregistry2.example.org/ns/foo:success
.Actual Behaviour
A change to the upstream image at
registry1.example.org/ns/foo:latest
is detected by theupstream
data source and successfully triggers thelocal
image resource to pull the image to the local docker instance. In my case, this is an ephemeral build server instance which disappears after the build pipeline regardless of success for failure, so this is seen as a new resource at every plan.However, because the values of the
docker_tag
'ssource_image
andtarget_image
technically never change, thedocker_tag
resource never detects source image change and thus the image is never published toregistry2...
.The text was updated successfully, but these errors were encountered: