What is the feature/update/fix?

Feature: Service Volume Support for convox run Command

We have added support for attaching service volumes when using the convox run command. This feature introduces a new --use-service-volume flag that automatically maps all volumes configured for a service to the run pod, ensuring that one-off processes have access to the same persistent storage as their parent service.

This resolves an issue where services scaled to zero that were executed with convox run would not properly attach to configured volumes, particularly EFS volumes. Now, when you run a one-off command with the --use-service-volume flag, the pod will inherit all volume configurations from the service definition.

Usage Example:

$ convox run web sh -a myapp --use-service-volume

Why is this important?

• Data Consistency: One-off processes can now access the same persistent volumes as regular service processes, ensuring data consistency across all operations
• Maintenance Operations: Enables running maintenance scripts, migrations, or data manipulation tasks with full access to persistent storage
• Debugging Capabilities: Allows developers to inspect and troubleshoot volume-mounted data through interactive shells
• Zero-Scale Services: Fixes the critical issue where services scaled to zero couldn't access their configured volumes when run as one-off processes

This feature is particularly valuable for:

• Running database migrations that need access to shared configuration files
• Executing batch jobs that process data stored on EFS volumes
• Debugging production issues by inspecting persistent volume contents
• Managing content in shared storage across multiple service instances

Does it have a breaking change?

No breaking changes are introduced with this update.

The feature is opt-in through the --use-service-volume flag. Existing convox run commands will continue to work as before without volume attachments unless the new flag is explicitly added.

Requirements

To use this feature, you must be on at least version 3.22.3 for both the CLI and the rack.

Update the CLI: Run convox update to update your CLI to the latest version. You can verify your CLI version with convox version.

For a minor version update, you must state the version with the command convox rack update 3.22.3 -r rackName.
You must be on at least rack version 3.21.0 to perform this update.

If you are unfamiliar with v3 rack versioning, we advise checking the documentation Updating a Rack