Unify 'abra server' command sequences #189

Closed
opened 2021-06-22 10:10:34 +00:00 by knoflook · 4 comments
Member

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:


  abra [options] server add <host> [<user>] [<port>]
  abra [options] server <host> rm
    

to:

  abra [options] server add <host> [<user>] [<port>]
  abra [options] server rm <host>
    

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>

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: ``` abra [options] server add <host> [<user>] [<port>] abra [options] server <host> rm ``` to: ``` abra [options] server add <host> [<user>] [<port>] abra [options] server rm <host> ``` 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 <app> to the end in all abra app commands, making it for instance:` abra app restore (<service>|--all) <app>`
decentral1se added the
design
label 2021-06-22 12:36:08 +00:00
decentral1se added this to the Beta release milestone 2021-06-22 12:36:10 +00:00
decentral1se added the
breaking-change
label 2021-06-22 12:58:20 +00:00
Owner

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.

  • possibly move to the end in all abra app commands, making it for instance: abra app restore (|--all)

Unsure but I see where you're going with this. 🤔

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. > - possibly move to the end in all abra app commands, making it for instance: abra app restore (<service>|--all) <app> Unsure but I see where you're going with this. 🤔
Author
Member

I think the intention is that the (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.

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 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. 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.
Owner

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

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
Owner

See you over in coop-cloud/go-abra#11!

Thanks for raising this 💯

See you over in [coop-cloud/go-abra#11](https://git.autonomic.zone/coop-cloud/go-abra/issues/11)! Thanks for raising this 💯
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/abra#189
No description provided.