mine isn't really a bug, it's more a behaviour change from version 2.25.0 to >= 3.0s.
I used to build docker images like in the posted code using docker_registry_image, by injecting different version, rebuild_trigger and commit_sha for each part of my application I could practically selectively decide from which image rebuild by changing those values.
Now that I upgraded the provider this trick sees to not be working anymore.
Is there a way to restore the previous behaviour?
Thank you.
Update
I tried now to use docker_registry_image but it still builds all the images:
Community Note
Terraform (and docker Provider) Version
Affected Resource(s)
docker_image
Terraform Configuration Files
Hi all,
mine isn't really a bug, it's more a behaviour change from version
2.25.0
to>= 3.0s
.I used to build docker images like in the posted code using
docker_registry_image
, by injecting differentversion
,rebuild_trigger
andcommit_sha
for each part of my application I could practically selectively decide from which image rebuild by changing those values.Now that I upgraded the provider this trick sees to not be working anymore.
Is there a way to restore the previous behaviour?
Thank you.
Update
I tried now to use
docker_registry_image
but it still builds all the images:I checked the passed
commit_sha
andrebuild_trigger
. Even changing them for just one part of the system, all the images are rebuilt.