We have a reasonably complex CI system and the managed railway deployments isn't cutting it for us anymore, mostly due to race conditions. I have built a solid workflow that creates new environments that we can use for deployments, but the problem is that these automatically spin up every service in our railway stack which we don't want. Also, they're made in the same section as our main production and development environments which is pretty bad for organization.

The ideal workflow would be:

1. Create a PR environment using the CLI.
2. Deploy services manually using CLI as needed.

This guide: https://docs.railway.com/guides/github-actions-pr-environment does not help here because the new environments automatically launch all the services in our stack which we explicitly do not want nor need.