Skip to content

Fix exit status code for convox exec command#855

Merged
nightfury1204 merged 1 commit intostagingfrom
fix-exec-exit-code
Jan 28, 2025
Merged

Fix exit status code for convox exec command#855
nightfury1204 merged 1 commit intostagingfrom
fix-exec-exit-code

Conversation

@nightfury1204
Copy link
Collaborator

@nightfury1204 nightfury1204 commented Jan 28, 2025

What is the feature/update/fix?

Fix: Corrected Exit Status Code for convox exec Command

This update resolves an issue where the convox exec command did not always return the correct exit status code. The command now properly reflects the exit code of the executed process inside the container, ensuring accurate handling in automation scripts and CI/CD workflows.

Why is this important?

Exit status codes are crucial for scripting and automation. Previously, incorrect or inconsistent exit codes from convox exec could cause confusion or unintended behavior in automated deployments, monitoring tools, and CI/CD pipelines. This fix ensures that:

  • A successful command inside the container returns a 0 exit code.
  • A failed command inside the container correctly propagates its non-zero exit code.
  • Scripts and automation that rely on convox exec can now function reliably without manual workarounds.

Does it have a breaking change?

No breaking changes are introduced with this update.

Requirements

To use this update, you must be on at least version 3.19.7.

For a minor version update, you must manually update your rack with the command convox rack update 3.19.7 -r rackName.
You must be on at least rack version 3.18.0 to perform this update.

If you are already on minor version 3.19.x, you can simply run convox rack update -r rackName.

If you are unfamiliar with v3 rack versioning, we advise checking the documentation Updating a Rack for more information before applying any updates.

@nightfury1204 nightfury1204 merged commit a17c7d2 into staging Jan 28, 2025
1 of 3 checks passed
@nightfury1204 nightfury1204 deleted the fix-exec-exit-code branch January 28, 2025 20:54
@nightfury1204 nightfury1204 mentioned this pull request Feb 3, 2025
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