Deleting projects through the CLI with `railway delete`

[sodic]

Old resources and issues (such as this one) suggests the Railway CLI once had a delete command. Are there any plans on bringing it back?

Motivation:

• At Wasp, we test our "Railway deployment" feature in the CI. After we're done with the testing, we must clean up the created projects. Calling railway delete <project-id> would be much nicer than doing two calls to the GraphQL API.
• I imagine the feature would be useful to anyone doing automated deployments and deletions (e.g., deploying a feature branch to test it, deleting the project once the branch is merged).
• It nicely rounds up Railway's terminal workflow. I can already do almost everything I need without leaving my terminal, deleting projects being the only exception. For that I have to use the dashboard.

I'd be happy to contribute and make this happen :)

[coffee-cup]

There is some hesitation in adding a delete command, especially with tools like Claude code often going rogue with deleting your projects. Maybe if there was some sort of --force or --long-and-scary flag?

[sodic]

Maybe if there was some sort of --force or --long-and-scary flag?

Sure, whatever works for you guys. Any simplification is welcome :)

Here's an argument on why I think we should have the delete command.

Claude can go rogue and delete projects by curling the GraphQL API. If it can't, that's only because the API is currently too complex for it. Let's say Claude gets better and learns how to delete projects with GraphQL consistently. I'm guessing we wouldn't then be dropping the GraphQL api as well :)

The point being: The better and more powerful a tool is, the easier it is to use - which is great!
But if a tool is easy to use, it's also easy to use recklessy. We shouldn't nerf or worsen our products to solve recklessness, regardless of who the reckless entity is - a human or an AI.

That said, people and AIs accidentally deleting projects is a real problem, and I agree we should try to mitigate it:

• One option is a --long-and-scary flag you suggested.

• Another option is interactively warning users that the action they're about to do is irreversible. We can ask them for confirmation or even to repeat the project's name (as Github does). For example, here's how fly does it:

  

@coffee-cup Let me know what you think.