Azure / Azure/static-web-apps-cli
Github actions deploying only to production instead of preview environments
- Vorherrschende Sprache
- TypeScript
- Sterne
- 668
- Forks
- 156
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
**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!
Beitragsleitfaden
Rechercherichtung
Beginnen Sie mit dem im Issue gezeigten GitHub Actions-Workflow und vergleichen Sie Deployments unter Verwendung der Image-Digests 6e8c2f7004cfd75ccbf2d1f5a402999432989eecd692d5536d47d46a07bb22ff und 870e5b73cf8d832615253d71b5834563b581a3fdfc26ccdfa264b37235. Untersuchen Sie das Verhalten der Azure Static Web Apps deploy action für Branches, die nicht main sind, und bestimmen Sie, ob Preview-Deployments wiederhergestellt werden, ohne die Produktion zu beeinflussen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, docker, github-actions
- Bereich
- ci-cd, cloud, devops
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100