Synchronous environment deletion (or status endpoint to confirm completion)
purduemike
PROOP
2 days ago
We use Railway to spin up ephemeral environments in a GitHub Actions merge queue. After calling environment delete, we need to immediately recreate an environment with the same name. Because deletion is asynchronous, the name isn't released right away and environment new fails with "already exists."
The workaround is to poll the environments query until the name disappears, but this adds complexity and latency to our CI pipeline.
We'd love either a --wait flag on environment delete that blocks until cleanup is complete, or a lightweight read endpoint to check whether an environment name has been fully released.
0 Threads mention this feature
0 Replies