Hi there !
Since this afternoon the deployments of my preview backend environments through the Koyeb’s Github action have been failing, see logs below. I suspect it could be due to the CLI’s new version release, but I’m not sure. Can you help troubleshooting? 
Thanks a lot!
Run koyeb/action-git-deploy@v1
Run if [ -z "preview-decide-pr-3021" ]; then
APP_SLUG=preview-decide-pr-3021
Run # sed: to replace non alphanum chars with -
SERVICE_SLUG=backend
Run /home/runner/work/_actions/koyeb/action-git-deploy/v1/scripts/app-create.py \
App preview-decide-pr-3021 already exists. Skip.
Run if [ -n "" ]; then
>> koyeb service get backend --app preview-decide-pr-3021 -o json
Service already exists. Triggering an update.
>> koyeb service update preview-decide-pr-3021/backend -o json --git github.com/jupi-co/decide --git-workdir '' --git-branch ra/2992/minor-ux-imporvements --git-sha '' --git-no-deploy-on-push --git-builder docker --git-docker-command '' --git-docker-args '' --git-docker-dockerfile apps/backend/Dockerfile --git-docker-target '' --git-docker-entrypoint '' --type web --instance-type small --regions par --env GOOGLE_CLIENT_SECRET=@prod-google-client-secret --env SUPERTOKENS_API_KEY=@prod-supertokens-api-key --env LIVEBLOCKS_SECRET_KEY=@staging-liveblocks-secret-key --env OPENAI_SECRET_KEY=@staging-openai-secret-key --env CLOUDFLARE_R2_TOKEN=@staging-cloudflare-r2-token --env CLOUDFLARE_S3_SECRET_ACCESS_KEY=@staging-cloudflare-s3-secret-access-key --env LANGFUSE_SECRET_KEY=@staging-langfuse-secret-key --env EXA_API_KEY=@staging-exa-api-key --env RESEND_API_KEY=@staging-resend-api-key --env ANTHROPIC_API_KEY=@staging-anthropic-api-key --env MISTRAL_API_KEY=@staging-mistral-api-key --env GROQ_API_KEY=@staging-groq-api-key --env DEEPSEEK_API_KEY=@staging-deepseek-api-key --env GOOGLE_API_KEY=@staging-google-api-key --env PERPLEXITY_API_KEY=@staging-perplexity-api-key --env CEREBRAS_API_KEY=@staging-cerebras-api-key --env XAI_API_KEY=@staging-xai-api-key --env FIRECRAWL_API_KEY=@staging-firecrawl-api-key --env TAVILY_API_KEY=@staging-tavily-api-key --env COURIER_API_KEY=@staging-courier-api-key --env STATSIG_API_KEY=@staging-statsig-api-key --env IP_API_SECRET_KEY=@staging-ip-api-secret-key --env AWS_ACCESS_KEY_ID=@staging-aws-access-key-id --env AWS_SECRET_ACCESS_KEY=@staging-aws-secret-access-key --env AZURE_OPENAI_API_KEY=@staging-azure-openai-api-key --env LINKUP_API_KEY=@staging-linkup-api-key --env QDRANT_API_KEY=@staging-qdrant-api-key --env AZURE_FOUNDRY_API_KEY=@staging-azure-foundry-api-key --env AI_GATEWAY_API_KEY=@staging-ai-gateway-api-key --env DATABASE_URL=@pr-3021-database-url --env DIRECT_DATABASE_URL=@pr-3021-direct-database-url --env PARTYKIT_SERVER=realtime-preview-pr-3021.jupi.co --env API_DOMAIN=https://jupi-pr-3021.koyeb.app --env WEBSITE_DOMAIN=https://decide-git-ra-2992minor-ux-imporvements-jupi-co.vercel.app --env NODE_ENV=preview --ports 3000:http --routes /:3000 --privileged=false --skip-cache=false
Traceback (most recent call last):
File "/home/runner/work/_actions/koyeb/action-git-deploy/v1/scripts/service-upsert.py", line 384, in <module>
main()
File "/home/runner/work/_actions/koyeb/action-git-deploy/v1/scripts/service-upsert.py", line 380, in main
koyeb_service_update(args.app_name, args.service_name, params)
File "/home/runner/work/_actions/koyeb/action-git-deploy/v1/scripts/service-upsert.py", line 261, in koyeb_service_update
raise RuntimeError(
RuntimeError: Error while updating the service backend
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
❌ Error while updating the service `preview-decide-pr-3021/backend`: the Koyeb API returned an unexpected error HTTP/200 that the CLI was unable to process, likely due to a bug in the CLI
🏥 How to solve the issue?
Please try upgrading to the latest version of the CLI. If the problem still persists, please open an issue at https://github.com/koyeb/koyeb-cli/issues/new and include the output of the command you ran with the --debug flag enabled.
🕦 The original error was:
DEPLOYMENT_STRATEGY_TYPE_DEFAULT is not a valid DeploymentStrategyType
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Process completed with exit code 1.