powerful-furniture-8375310/20/2021, 12:51 PM
tag isn't updating the lambda. How can we force the lambda to refetch the docker image? Or do we have to have well named version tags and that then forces the lambda to update?
great-sunset-35510/20/2021, 2:48 PM
tag is not a good idea, so I'd listen to the service and rather tag the image with commit SHA (or version or anything) on rebuild.
And simple dev purposes you can always push 2 tags. 1 with SHA and 2nd latest
powerful-furniture-8375310/20/2021, 2:54 PM
great-sunset-35510/21/2021, 6:41 AM
is concurrency. Imagine your lambda is executed 100k times in parallel with a small-time drift.
And somewhere in between 50k - 70k you update the image. You'd end up with half of your code executed using a new version and half the old version. (pure nightmare)
Alternative would be that lambda has to pull the image every time, but that's not possible because of Cold/Hot state lambda has.
So any use cases considering not updating the lambda should be seriously reconsidered or use a different service.