Azure / Azure/static-web-apps-cli
Github actions deploying only to production instead of preview environments
- Lingua principale
- TypeScript
- Stelle
- 668
- Fork
- 156
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**Describe the bug**
I have noticed the last few github action builds have been deployed to the production website instead of the preview environment.
The workflow file hasn't changed and the branch is not the main branch.
This seems to have happened since the docker image at mcr.microsoft.com/appsvc/staticappsclient:stable was updated.
The last successful run was when github actions was using the docker image with a sha digest of:
6e8c2f7004cfd75ccbf2d1f5a402999432989eecd692d5536d47d46a07bb22ff
This issue started happening since the stable docker image was updated with a sha digest of:
870e5b73cf8d832615253d71b5834563b581a3fdf1a3defc26ccdfa264b37235
**Github actions**
```
- name: Build And Deploy
id: builddeploy
uses: Azure/static-web-apps-deploy@v1
with:
azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_BLUE_COAST_044CD3B03 }}
repo_token: ${{ secrets.GITHUB_TOKEN }}
action: "upload"
app_location: "/"
api_location: "api/api"
output_location: "dist"
production_branch: "main"
```
**Screenshots**
This is what used to happen:

And now it's not going to a develop preview environment:

Hopefully this issue can be fixed. Happy to provide more details if needed.
Really enjoying Static Web Apps by the way. Great work!
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con il workflow GitHub Actions mostrato nell’issue e confronta i deployment utilizzando gli image digest 6e8c2f7004cfd75ccbf2d1f5a402999432989eecd692d5536d47d46a07bb22ff e 870e5b73cf8d832615253d71b5834563b581a3fdfc26ccdfa264b37235. Esamina il comportamento di Azure Static Web Apps deploy action per i branch diversi da main e determina se i preview deployment vengono ripristinati senza influire sulla produzione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- azure, docker, github-actions
- Ambito
- ci-cd, cloud, devops
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100