Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: deploy falsely reports SUCCESS when it failed #1091

Closed
wants to merge 1 commit into from

Conversation

elrayle
Copy link
Collaborator

@elrayle elrayle commented Apr 10, 2024

Multiple issues are fixed in this PR:

  • If the webapp publish profile secret is empty, webapps-deploy v3 doesn’t deploy but reports the deploy as passing. See Azure/webapps-deploy Issue #404.
  • Configs were set before running the deploy. This means that the config values in Azure are updated even if the deploy fails.
  • The action was runnable by anyone with write access. That is too broad for production.

To avoid these known issues, the PR updates to...

  • check that all required secrets are set before proceeding
  • only update configs if the deploy passes
  • call the reusable workflow that checks if the user has access to deploy

@elrayle elrayle changed the title fix deploy falsely reports deploy SUCCESS when it failed fix: deploy falsely reports SUCCESS when it failed Apr 10, 2024
@elrayle elrayle force-pushed the elr/org-secrets branch 4 times, most recently from 369acb9 to 4c5d610 Compare April 11, 2024 01:57
@elrayle elrayle marked this pull request as draft April 11, 2024 16:22
Several issues were identified with the workflow:
* If the webapp publish profile secret is empty, webapps-deploy v3 doesn’t deploy but reports the deploy as passing.  See Azure/webapps-deploy [Issue #404](Azure/webapps-deploy#404).
* Configs were set before running the deploy.  This means that the config values in Azure are updated even if the deploy fails.
* As written, the action was runnable by anyone with write access.  That is too broad for production.

To avoid these known issues:
* check that all required secrets are set before proceeding
* call the reusable workflow that checks if the user has access to deploy

_NOTE: Configs cannot be moved after the deploy because they are used by the restart process kicked of by the deploy._
@elrayle
Copy link
Collaborator Author

elrayle commented Apr 15, 2024

This is superseded by the work in:

The new PRs combine the dev and deploy workflows into a single shared workflow in operations.

@elrayle elrayle closed this Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant