Azure Static Web app deployes locally but not in CI/CD CircleCI

[Judimax]

Before filing this issue, please ensure you're using the latest CLI by running swa --version and comparing to the latest version on npm.

Are you accessing the CLI from the default port :4280 ?

• [*] No, I am using a different port number (--port) I dont even use a port to deploy
• Yes, I am accessing the CLI from port :4280

Make sure you are accessing the URL printed in the console when running swa start!

ℹ️ NOTE: Make sure to enable debug logs when running any swa commands using --verbose=silly

Describe the bug
A clear and concise description of what the bug is.

Could not find StaticSitesClient local binary

To Reproduce
Steps to reproduce the behavior:

config.zip
use the config.yml as you push a new commit to your master branch
let the pipeline run
you get the error

Expected behavior
A clear and concise description of what you expected to happen.
it has the binary and it can get to it locally or globally when npx is used, it should have no problem deploying

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[sgollapudi77]

Hi @MichaelOdumosu57, you will get this error if you don't have the StaticSiteClient installed locally or if it is not the latest version. But after this warning, SWA_CLI downloads the binary and deployment should happen without any error. Please refer to this TSG or re-open the issue if you face any issues with the deployment.

[Judimax]

Tried to follow this steps in the TSG however issue, the sha256 keeps on coming up as different every time

[Judimax]

@sgollapudi77 can you reopen and take a look at the dockerfile commands used to create the docker image as well as the script used to run swa code in question

# add StaticSitesClient binary
ENV    STATIC_SITES_BINARY  "https://swalocaldeploy.azureedge.net/downloads/1.0.020981/linux/StaticSitesClient"
# RUN echo "export STATIC_SITES_BINARY_VERSION=$(echo $STATIC_SITES_BINARY | grep  -o  -E '[0-9].+[0-9]+')" >> /root/.bashrc
ENV   STATIC_SITES_BINARY_VERSION 1.0.020981
ENV    SWA_CLI_DEPLOY_BINARY  /root/.swa/deploy/1.0.020981/StaticSiteClient


RUN mkdir -p $(dirname $SWA_CLI_DEPLOY_BINARY) && touch $SWA_CLI_DEPLOY_BINARY;\
    wget -o $SWA_CLI_DEPLOY_BINARY $STATIC_SITES_BINARY;\
    STATIC_SITES_BINARY_CHECKSUM=$(sha256sum $SWA_CLI_DEPLOY_BINARY | head -c 64);\
    STATIC_SITES_BINARY_JSON=$HOME/.swa/deploy/StaticSitesClient.json;\
    mkdir -p $(dirname $STATIC_SITES_BINARY_JSON) && touch $STATIC_SITES_BINARY_JSON;\
    echo '{"metadata":   {"version": "stable","buildId": "'$STATIC_SITES_BINARY_VERSION'","publishDate": "2022-09-29T17:37:34.4094014Z","files": {"linux-x64": {"url": "https://swalocaldeploy.azureedge.net/downloads/1.0.020981/linux/StaticSitesClient","sha": "e55db21d0720a12098804559152303e66846bdd94c13a30b30be29a0fc9ae366"},            "win-x64": {        "url": "https://swalocaldeploy.azureedge.net/downloads/1.0.020981/windows/StaticSitesClient.exe",        "sha": "4e4eb72aef26641e236c24929c822500e956bda099ca78054112cadf20261107"      },      "osx-x64": {        "url": "https://swalocaldeploy.azureedge.net/downloads/1.0.020981/macOS/StaticSitesClient",        "sha": "e0f2ae7ec297510a1b3b9332c0dc0dd962a51adb8ea13cd4f3746d79fc24a7e9"      }    }  },    "binary":"'$HOME'/.swa/deploy/'$STATIC_SITES_BINARY_VERSION'/StaticSitesClient",    "checksum":"'$STATIC_SITES_BINARY_CHECKSUM'"}' >> $STATIC_SITES_BINARY_JSON;

• the env vars are keps in the secrets for the CI/CD software

          npm run build;
          npx swa deploy ./dist/azureSWA  --env production  --app-name nibls-angular-frontend-0;

[subesokun]

@Judimax Is it possible to pre-download the SWA CLI binaries (like a swa init-cli)? I want to avoid any downloads during runtime and have the SWA CLI already included in my container image, which is used for CI/CD tasks.