#short-flags in `dagger call`
1 messages · Page 1 of 1 (latest)
(Worth noting up -n should just be the default, and exec -it will probably be a dedicated command that implies -it instead of exec. Just didn't have better examples ready.)
what flags are candidates to have a short version at the moment?
dagger up used to have -n, not sure if that survived the transition to the new CLI, or if has been made the default already
I think it's very clear how it would be implemented (pragmas+annotations in SDKs, Field setting in dagql, etc.) and would just amount to a lot of plumbing. I just think it's a situation where we should wait to see if the need really arises strongly in practice. Otherwise we're layering on more maintainance burden. Not so much to inherently rule it out, but enough that the cost should be justified. IMO.
Default is "choose random ports", so yeah you have to type out --native now if you want it
Can adjust the defaults too of course
Tempting to just cheat and take the first letter of each arg, but there are probably too many places where it's ambiguous
So yeah if it involves a lot of plumbing I think we'd need a really strong need, I'm good with keeping a high bar and seeing what flags hurt to use all the time first (if any)
I can put up a quick PR, I think there's consensus on this already, just never got triaged
Sure, I do want to make sure that it's still relatively easy to go to "use random available ports for everything", but can discuss on PR
It seems in most cases we want --native to be the default. So this makes it the default and adds --random for the old behavior (choose random ports).
(hey nice, no more ginormous avatars in GH embeds?)
Right now, export --path for a Directory, for example, has short form of -o, right?