i had the same issue with the different terraform versions in my build and deploy stage VM's about 6 months ago🤦♂😂... sent me in a spin, sometimes it work sometimes it didn't... i think i added a terraform install task in both stages so it installed the lastest (or preferred) version
It’s wild that this would be possible or at least very likely. Do you think we are just unlucky? 🤣 I mean I’m sure these host pools are pulling the same VM image….unless there is a tiny window where rolling updates haven’t incremented the version of the VM image and we just managed to thread the needle…
@@azure-terraformer yea, that was the conclusion i came to.... they must have a whole load of vms provisioned waiting to be used possibly they were provisioned in between the images being updated, so potential for a cross over issue 🤷♂🤷♂ but fixed when pinned to a version... still remember scratching my head for a while when it happened... as always it was as i was demonstrating it to someone too 😂😂
i had the same issue with the different terraform versions in my build and deploy stage VM's about 6 months ago🤦♂😂... sent me in a spin, sometimes it work sometimes it didn't... i think i added a terraform install task in both stages so it installed the lastest (or preferred) version
It’s wild that this would be possible or at least very likely. Do you think we are just unlucky? 🤣 I mean I’m sure these host pools are pulling the same VM image….unless there is a tiny window where rolling updates haven’t incremented the version of the VM image and we just managed to thread the needle…
@@azure-terraformer yea, that was the conclusion i came to.... they must have a whole load of vms provisioned waiting to be used possibly they were provisioned in between the images being updated, so potential for a cross over issue 🤷♂🤷♂ but fixed when pinned to a version... still remember scratching my head for a while when it happened... as always it was as i was demonstrating it to someone too 😂😂
Oh man the demo gods strike again!!! 🤣