Azure deployment configuration does not always take the latest patch.

[malavvvakharia]

mcr.microsoft.com/azureiotedge-metrics-collector:1.1

Expectation: In many container registries, using a tag like 1.1 implies that the system will pull the latest patch version within the 1.1.x series (e.g., 1.1.2, 1.1.3, etc.).

Reality in Azure IoT Edge: When deploying modules via IoT Hub, the deployment manifest does not automatically resolve to the latest patch version. Instead, it pulls exactly the version specified in the tag. So 1.1 will pull the image tagged 1.1, not 1.1.x.

[vadim-kovalyov]

Hi @malavvvakharia, the 1.1 tag is a floating tag that points to the latest 1.1.x version. So, for example, if 1.1.4 image is posted, the 1.1 tag is also updated to point to it.

[malavvvakharia]

Hi @vadim-kovalyov , That was my assumption, but do you know how to verify it? According to me, it should be shown in the reported property.

[vadim-kovalyov]

@malavvvakharia

You can always compare the digest of the images to see that they are identical. You can do that by pulling images or also go to the MCR portal and see it there - https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-metrics-collector/tags

[malavvvakharia]

@vadim-kovalyov , Thank you so much, it helps a lot.