Allow creation of OAuth connections without an alias

[Aidan Harding]

When creating a new OAuth connection from the Manage Connections window, IC requires an alias. When I’m connecting to a sandbox/prod org, the username itself is a handy unique name for the connection. So, when I do this through the CLI, I don’t supply an alias.

It would be nice to have the same possibility in IC.

[Scott Wells]

I'll have to chew on this one a bit. The alias ends up being the connection name in IC2. Connection names also provide a level of indirection for project config, especially when checked into version control for a team. That allows a single project config to be used across all team members where a name/alias like sandbox can point at whichever org is needed by each team member vs. a username which is typically going to be unique per-user.

[Aidan Harding]

Hey Scott,

The strong use-case here is for OAuth connections to production. There’s no better alias in my mind than the unique username for that connection.

Also, our common use-case here is for sandboxes that correspond to feature branches. To start work, I need a CLI connection so that I can push/pull. I could create that from the CLI, but it’s nice to make it directly in IC.

I agree that it should have an alias for scratch orgs. And can have a username for sandboxes. But for prod, no alias is useful.

[Scott Wells]

Removing version: Unassigned (automated comment)