abra app restart help & --all #605

Open
opened 2024-04-04 13:05:30 +00:00 by decentral1se · 1 comment
Owner

It takes a <service> argument, it doesn't restart every service. The help doesn't reflect that.

See https://codeberg.org/eotl/sextant/issues/94#issuecomment-1732145 for confusion.

I believe it could be useful to cycle through all services if --all is passed perhaps @basebuilder?

abra app restart -h
NAME:
abra app restart - Restart an app

USAGE:
abra app restart [command options]

DESCRIPTION:
This command restarts a service within a deployed app.

OPTIONS:
--debug, -d Show DEBUG messages
--offline, -o Prefer offline & filesystem access when possible

It takes a `<service>` argument, it doesn't restart every service. The help doesn't reflect that. See https://codeberg.org/eotl/sextant/issues/94#issuecomment-1732145 for confusion. I believe it could be useful to cycle through all services if `--all` is passed perhaps @basebuilder? > abra app restart -h > NAME: > abra app restart - Restart an app > > USAGE: > abra app restart [command options] <domain> > > DESCRIPTION: > This command restarts a service within a deployed app. > > OPTIONS: > --debug, -d Show DEBUG messages > --offline, -o Prefer offline & filesystem access when possible
decentral1se added the
bug
abra
labels 2024-04-04 13:05:30 +00:00
Member

It takes a argument, it doesn't restart every service.

What a <service> arg means in this case is just a guess for me... I think I tried all of the following:

  • sextant.eotl.dev
  • sextant.eotl.dev:app
  • sextant:app

In the case of sextant there is only app service.

🔴 Fail - What I imagine would be intuitive for apps with multiple services is to restart all run:

abra app restart sextant.eotl.dev
ERRO[0000] missing service?  

🔴 Fail - Or to restart the specific badger service within that app deployment

abra app restart sextant.eotl.dev:badger
FATA[0000] cannot find app with name sextant.eotl.dev:app 

Success - with the <service> as a separate word after the app

abra app restart sextant.eotl.dev app
INFO[0016] app service successfully restarted 

So yah, I think the syntax is fine, just the helper needs to make this clear

> It takes a <service> argument, it doesn't restart every service. What a `<service>` arg means in this case is just a guess for me... I think I tried all of the following: - `sextant.eotl.dev` - `sextant.eotl.dev:app` - `sextant:app` In the case of `sextant` there is only `app` service. 🔴 Fail - What I imagine would be intuitive for apps with multiple services is to restart all run: ``` abra app restart sextant.eotl.dev ERRO[0000] missing service? ``` 🔴 Fail - Or to restart the specific `badger` service within that app deployment ``` abra app restart sextant.eotl.dev:badger FATA[0000] cannot find app with name sextant.eotl.dev:app ``` ✅ Success - with the `<service>` as a separate word after the app ``` abra app restart sextant.eotl.dev app INFO[0016] app service successfully restarted ``` So yah, I think the syntax is fine, just the helper needs to make this clear
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
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/organising#605
No description provided.