Skip to content

feat(volume): show status and scheduled deletion date in volume list#928

Merged
JakeCooper merged 1 commit into
masterfrom
cooper/volume-deletion-status
Jun 3, 2026
Merged

feat(volume): show status and scheduled deletion date in volume list#928
JakeCooper merged 1 commit into
masterfrom
cooper/volume-deletion-status

Conversation

@JakeCooper
Copy link
Copy Markdown
Contributor

What

railway volume list now shows each volume's lifecycle status and, for volumes that are pending deletion, a "Deletes on" date — mirroring the "This volume is scheduled for deletion on …" banner in the dashboard so users can see and act on it from the CLI.

Why

When a volume is orphaned/detached it gets scheduled for permanent deletion, and the dashboard surfaces both the state and the deletion date with a restore CTA. The CLI gave no indication at all, so users driving Railway from the terminal had no way to know a volume's data was about to be purged.

Changes

  • Fetch state, deletedAt, and isPendingDeletion on volume instances in the Project query (and add the fields to the local introspection schema.json).
  • Print a colored Status: line for every volume (green = Ready, red = Deleting/Deleted/Error, yellow = Migrating/Restoring/Updating/…).
  • Print a red Deletes on: line (rendered in local time) when a volume isPendingDeletion.
  • Include status, isPendingDeletion, and deletedAt (RFC 3339) in --json output.

Example

Volume: meilisearch-volume
Attached to: meilisearch
Mount path: /meili_data
Storage used: 5234MB/10240MB
Status: Deleting
Deletes on: Jun 3 2026 4:24 PM PDT

🤖 Generated with Claude Code

@JakeCooper JakeCooper added the release/patch Author patch release label Jun 3, 2026
`railway volume list` now surfaces each volume's lifecycle state and, for
volumes pending deletion, the date the data will be permanently removed —
mirroring the "scheduled for deletion" banner in the dashboard so users can
see and act on it from the CLI.

- Fetch `deletedAt` and `isPendingDeletion` on volume instances (state was
  already queried)
- Print a colored "Status:" line for every volume
- Print a red "Deletes on:" line (local time) when a volume is pending deletion
- Include `status`, `isPendingDeletion`, and `deletedAt` in `--json` output

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@JakeCooper JakeCooper force-pushed the cooper/volume-deletion-status branch from 75d86fd to 484fba6 Compare June 3, 2026 02:39
@JakeCooper JakeCooper merged commit e1add58 into master Jun 3, 2026
7 checks passed
@JakeCooper JakeCooper deleted the cooper/volume-deletion-status branch June 3, 2026 02:41
codyde added a commit that referenced this pull request Jun 4, 2026
…-browser-login

* origin/master: (28 commits)
  chore: Release railwayapp version 5.0.0
  feat(sandbox): fork, templates, and `--variable`/`--env-file` on create (#933)
  chore: Release railwayapp version 4.68.0
  feat(volume): include modified time in files JSON (#931)
  chore: Release railwayapp version 4.67.0
  Add service source connection support (#934)
  chore: Release railwayapp version 4.66.2
  Make GraphQL HTTP timeout configurable via RAILWAY_HTTP_TIMEOUT (#932)
  chore: Release railwayapp version 4.66.1
  feat(volume): show status and scheduled deletion date in volume list (#928)
  SSH Command: Handle Identity Files (#926)
  chore: Release railwayapp version 4.66.0
  feat(sandbox): `railway sandbox` commands (create/list/ssh/exec/destroy) (#925)
  chore: Release railwayapp version 4.65.0
  SSH Agent Support, `russh` edition. (#915)
  chore: Release railwayapp version 4.64.0
  chore: Release railwayapp version 4.63.0
  Rephrase agent advisory and gate by CLI version (#919)
  Forward --remote to setup agent in cli.new installer (#918)
  chore: Release railwayapp version 4.62.0
  ...

# Conflicts:
#	src/consts.rs
#	src/util/mod.rs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release/patch Author patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant