In general: how do we feel about thecreate andedit subcommands (versus justcreate in master)?
I feel it's more sensible from a user standpoint to make separate verbs.. and non-intuitive thatcreate could alsoupdate an existing devurl. If no one has objections, I'd like to makecreate actually refuse to update an existing devurl, and letedit do that.

The downside is thatcreate would then no longer be an idempotent operation; callers of coder-cli would need to take into account the state of the environment: whether a devurl already exists or not, in order to use the appropriate subcommand.

An alternative could be to add a flag tocreate e.g.

$ coder create -m <env> <port>

Where-m would mean 'create, or modify if already existing'. Not specifying-m would then meancreate would refuse to modify existing devurls. We could keepedit as a separate modify-only subcommand, or do away with it.

Regarding the create/edit subcommands, I'd prefer to either keep how you have it right now in the pr, or go back to having justcreate. Personally, I like that it's idempotent(ish) and I'd find it annoying to have to calledit in the case of me forgetting that a devurl already exists. I like my CLIs to just do what I mean.

Sure. Since@fuskovic added an alias ability to the cli recently, I left in "edit", but one can just usecreate for both ops.

@Russtopia Anything blocking this from merging?