Failed to get device type build data for... about open-balena HOT 2 CLOSED

For anyone else following along, esr-images contains the "Extended Support Release" images as detailed here and is a very limited set of devices:

• beaglebone-black
• ccon-01
• fincm3
• genericx86-64-ext
• intel-nuc
• jetson-tx2
• raspberry-pi
• raspberrypi3-64
• raspberrypi3
• raspberrypi4-64
• revpi-connect
• rockpi-4b-rk3399
• skx2

... so, esr-images is not what I wanted, as it is missing the 3 device types I actually need 😅

As for the errors, there seem to be certain device types where everything has permissions set to not allow public access for reading files, but still allows listing files. For example, the error above is trying to read https://resin-production-img-cloudformation.s3.amazonaws.com/images/imx8mmebcrs08a1/2.100.3/device-type.json which gives access denied (as does every other file in images/imx8mmebcrs08a1/*), this causes contractSync to be able to enumerate the files but not fetch the device-type.json and thus the open-balena-api log gets flooded with these errors on first sync.

Seems like there are two possible fixes:

1. Fix resin-production-img-cloudformation permissions on these device types to either prohibit both LIST and GET, or permit GET.
2. Create a new ENV variable that can be set for open-balena-api that allows for a list of device-types we actually want. For example: INCLUDE_IMAGES=iot-gate-imx8,generic-amd64,generic-aarch64 which could filter both the device type contracts pulled from https://github.com/balena-io/contracts and the device type information pulled from https://resin-production-img-cloudformation.s3.amazonaws.com/images/ ... as I would assume no open-balena instance actually needs every possible device type - and if they do, they can just not set INCLUDE_IMAGES and it would fall back to the current behavior of grabbing everything.

from open-balena.

Closing in favor of balena-io/open-balena-api#1433

from open-balena.