This message was deleted.

Hi, yeah I guess that is a bit confusing because we don’t modify the install script with the version so it’s always pointed to the latest. The binaries for each release are available as release assets so if you look at the release page for 0.10.16 in the assests section you’ll see the binaries for each arch/platform, e.g. https://github.com/infracost/infracost/releases/download/v0.10.16/infracost-linux-amd64.tar.gz

Yes, that’s what I did before the multi arch, but the installer is very convenient to avoid this kind of logic in Dockerfile

RUN set -eux; \
    case "${TARGETPLATFORM}" in \
      linux/amd64)  \
        AWSCLI='awscli-exe-linux-x86_64.zip'  \
        ARCH="amd64"  \
      ;; \
      linux/arm64|linux/arm/v8)  \
        AWSCLI='awscli-exe-linux-aarch64.zip'  \
        ARCH="arm64"  \
      ;; \
	esac;\
curl -L "<https://github.com/infracost/infracost/releases/download/v${INFRACOST}/infracost-linux-${ARCH}.tar.gz>" | tar -zx -C /usr/local/bin/

yeah that makes sense if we let you provide the version as an env or a flag. (probably would want to call the env

INFRACOST_VERSION

to avoid collisions)

not sure you can pass a flag when you pipe the download to sh ?

INFRACOST_VERSION

LGTM

yeah that would be great

I’m not allowed to add reviewers but here is the PR https://github.com/infracost/infracost/pull/2251

This is merged to master if you want to try it out

I got the notification, thank you