Exit code 1 after deployed successfully

When deploying with flyctl deploy, the deployment succeeds but the command returns an exit code 1 and fails the github action.

I reviewed this post however this is not an acceptable work around as the CI/CD checks will still fail and PRs will not be automatically approved.

==> Creating release
--> release v2 created

--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: yarn deploy

--> This release will not be available until the release command succeeds.
	 Unpacking image
	 2022/10/19 01:33:15 listening on [fdaa:0:bacf:a7b:9c3e:b50a:1b95:2]:22 (DNS: [fdaa::3]:53)
	 yarn run v1.22.19
	 $ keystone prisma migrate deploy
	 Unpacking image
	 Starting init (commit: 249766e)...
	 UUID=8fa8e6fa-5586-4fae-b934-16f2ea9706bc
	 2022/10/19 01:33:15 listening on [fdaa:0:bacf:a7b:9c3e:b50a:1b95:2]:22 (DNS: [fdaa::3]:53)
	 yarn run v1.22.19
	 $ keystone prisma migrate deploy
	 Datasource "postgresql": PostgreSQL database "focapp_benefit_has_its_own_color_cms", schema "public" at "top2.nearest.of.focapp-benefit-has-its-own-color-db.internal:5432"
	 Datasource "postgresql": PostgreSQL database "focapp_benefit_has_its_own_color_cms", schema "public" at "top2.nearest.of.focapp-benefit-has-its-own-color-db.internal:5432"
	 Applying migration `20[221](https://github.com/applyinnovations/focapp/actions/runs/3278128907/jobs/5396196697#step:4:222)014080127_update_user_attributes`
	 Applying migration `20221019011136_added_initial_data_validation_and_required_fields`
	 Done in 9.75s.
	 Applying migration `20221014080127_update_user_attributes`
	 Applying migration `20221019011136_added_initial_data_validation_and_required_fields`
	 Done in 9.75s.
	 Starting clean up.
	 Starting clean up.
	 Unpacking image
	 Starting init (commit: 249766e)...
	 UUID=8fa8e6fa-5586-4fae-b934-16f2ea9706bc
	 2022/10/19 01:33:15 listening on [fdaa:0:bacf:a7b:9c3e:b50a:1b95:2]:22 (DNS: [fdaa::3]:53)
	 yarn run v1.22.19
	 $ keystone prisma migrate deploy
	 Datasource "postgresql": PostgreSQL database "focapp_benefit_has_its_own_color_cms", schema "public" at "top2.nearest.of.focapp-benefit-has-its-own-color-db.internal:5432"
	 Applying migration `20221014080127_update_user_attributes`
	 Applying migration `20221019011136_added_initial_data_validation_and_required_fields`
	 Done in 9.75s.
	 Starting clean up.
==> Monitoring deployment

v0 is being deployed
609f69b0: syd running healthy
609f69b0: syd running unhealthy [health checks: 1 total, 1 critical]
609f69b0: syd running healthy [health checks: 1 total, 1 passing]
--> v0 deployed successfully
Error: Process completed with exit code 1.

Interesting! I haven’t seen that reported before within GHA.

  1. Is that the latest version of fly? (likely yes if using the fly “action”
  2. Would you be able to try that again use env var LOG_LEVEL=debug?

If you can get that behavior locally it’ll be easier than testing in github actions.