Feature request: service aliases

[brettchalupa]

Service IDs are difficult to remember, and I'd like an easy way to reference a service by an alias that I can configure.

So, for example, let's say I have Service with ID srv-abc123 that's a Ruby server running Rails. In my head, I refer to it as rails.staging, I'd like to be able to run: render ssh rails.staging

Then for my production service, I could create an alias and SSH in like render ssh rails.prod

The interface for working with aliases could be something like: render alias create rails.staging ➡️ which then shows the TUI selector for services.

The implementation could be something like that alias mapping gets stored in the local YAML config file that the workspace is stored in. And when a command is run, it checks for the alias to get the Service ID.

[davidharting]

In some placse through render CLI, we accept names instead of IDs. render ssh is one of those places!

We do not plan on supporting service aliases, but would using service name help? Or are your service names ambiguous (i.e.,, multiple services with the same name in a single workspace?)

e.g., if you have a service called prod-rails-web you could do render ssh prod-rails-web

[brettchalupa]

@davidharting being able to use service names would definitely help! For the services we have, we give them all unique names per environment so it's easy to identify them. For example, rails-prod, sidekiq-prod, rails-staging. So that would totally meet the needs and make it easier to use.