Unify 'abra server' command sequences #189
Labels
No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
No Milestone
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#189
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently abra doesn't have the same argument sequence for adding and removing a server (also applies to init etc.). I suggest using the same sequence for every command, thus changing:
to:
it's more intuitive that way. Here's a list of commands that I propose to change:
recipe:
- release
- versions
server:
- rm
- init
- apps
app:
- possibly move to the end in all abra app commands, making it for instance:
abra app restore (<service>|--all) <app>
Interesting!
I think the intention is that the
<cmd>
(e.g.rm
) would come at the end so it is convenient to run other commands, you'd just have to backspace a little bit. But then the<host>
positioning having different order, that is true.@3wordchant curious on your thoughts.
Unsure but I see where you're going with this. 🤔
Then we could change the
abra server add
positioning! You're more likely to do a few operations on the same host/app than to do the same operation on a few different hosts/apps. On the other hand, if you want to add a couple of hosts it makes more sense to have the host as the last argument. Uhh, I'm at a loss here.I am planning something like this with the go port I am doing of abra. Had some discussions with some Autonomic members to think about some solutions
See you over in coop-cloud/go-abra#11!
Thanks for raising this 💯