Deployment issues - CICD

I have deploying to prod yaml and it is failing with errors from Gadget, it used to work a couple of weeks ago, but now it does not. What changed? It's failing wiht such errors:
Aborting because ggt is not running in an interactive terminal.
Error: Process completed with exit code 1.
Aborting because ggt is not running in an interactive terminal.
Error: Process completed with exit code 1.
And this is the yaml:
name: Deploy to Production

on:
push:
branches:
- main

jobs:
deploy:
runs-on: ubuntu-latest

steps:
- name: Checkout code
uses: actions/checkout@v4

- name: Install Gadget CLI
run: |
npm install -g ggt@latest
ggt version

- name: Deploy to production.
run: |
ggt deploy --app=my-app --env=development --force --allow-unknown-directory
shell: bash
env:
GGT_TOKEN: ${{ secrets.GGT_TOKEN }}
name: Deploy to Production

on:
push:
branches:
- main

jobs:
deploy:
runs-on: ubuntu-latest

steps:
- name: Checkout code
uses: actions/checkout@v4

- name: Install Gadget CLI
run: |
npm install -g ggt@latest
ggt version

- name: Deploy to production.
run: |
ggt deploy --app=my-app --env=development --force --allow-unknown-directory
shell: bash
env:
GGT_TOKEN: ${{ secrets.GGT_TOKEN }}
I see similar issue in https://discord.com/channels/836317518595096598/1291605130269163552
4 Replies
Chocci_Milk
Chocci_Milk4w ago
Hello, Could you please run ggt with the --telemetry flag on so that we can get some diagnositcs as to what might be going on? Have you also tried adding more allow flags to the deploy command? https://docs.gadget.dev/reference/ggt#:~:text=to%20%22.%22%20(current%20directory).-,Options,-%2Da
emabaran
emabaranOP4w ago
that’s strange now it works, I did not change anything… sorry for bothering then 😄
Chocci_Milk
Chocci_Milk4w ago
No problem. Do you mind still using the telemetry flag just in case this happens again
Gizmo
Gizmo4w ago
Do you like this answer? ​

Did you find this page helpful?