Add flag to aid in debugging abra server add #587

New Issue

2024-03-26T18:07:13Z

basebuilder commented

2024-03-26 18:07:13 +00:00

Recently a new abra user asked for support in #coopcloud-tech to debug why they could not successfully complete the abra server add <server> command.

The issue this newbie encountered was that their SSH connection was using a different user on their client machine than the user that what was available on the server they were trying to connect to (in the add sub-command).

Explicitly specifying the User value in the ~/.ssh/config file is one configuration method of avoiding this issues. However, as related issues #567 #566 #570 getting these configs right is tricky business.

It was suggested by @decentral1se that maybe adding a flag like abra server add --fuck could print what abra is intending to do in human friendly language such as which user, domain, ssh opts etc. Other names for this flag could be:

--deets
--d33ts
--halp
--print
--details

Alternatively abra could just show this information at start of --debug command

Recently a new `abra` user asked for support in [#coopcloud-tech](https://matrix.to/#/#coopcloud-tech:autonomic.zone) to debug why they could not successfully complete the `abra server add <server>` command. The issue this newbie encountered was that their SSH connection was using a different `user` on their client machine than the user that what was available on the server they were trying to connect to (in the `add` sub-command). Explicitly specifying the `User` value in the `~/.ssh/config` file is one configuration method of avoiding this issues. However, as related issues #567 #566 #570 getting these configs right is tricky business. It was suggested by @decentral1se that maybe adding a flag like `abra server add --fuck` could print what `abra` is intending to do in human friendly language such as which user, domain, ssh opts etc. Other names for this flag could be: ``` --deets --d33ts --halp --print --details ``` Alternatively `abra` could just show this information at start of `--debug` command

❤️ 1

basebuilder added the enhancement abra labels 2024-03-26 18:07:13 +00:00

decentral1se commented

2024-06-22 12:40:43 +00:00

@basebuilder following coop-cloud/abra#413 I'm wondering how to proceed on this one. It seems more like a documentation issue at this point, involving pointing people to the appropriate usage of ssh -vvv ... to discover exactly what goes on under the hood. All abra does now is run ssh <Host> .... Whatcha reckon?

There's a few SSH related tickets floating around which are related which I'm trying to triage now also.

@basebuilder following https://git.coopcloud.tech/coop-cloud/abra/pulls/413 I'm wondering how to proceed on this one. It seems more like a documentation issue at this point, involving pointing people to the appropriate usage of `ssh -vvv ...` to discover exactly what goes on under the hood. All `abra` does now is run `ssh <Host> ...`. Whatcha reckon? There's a few SSH related tickets floating around which are related which I'm trying to triage now also.

decentral1se commented

2024-07-07 10:29:40 +00:00

Seems resolved since the latest changes in SSH config handling. See tickets under "general fixes / improvements" on coop-cloud/organising#583. (TLDR; ssh -v tells you everything, abra does nothing additional now) There were also a few docs patches pushed.

Seems resolved since the latest changes in SSH config handling. See tickets under "general fixes / improvements" on https://git.coopcloud.tech/coop-cloud/organising/issues/583. (TLDR; `ssh -v` tells you everything, `abra` does *nothing* additional now) There were also a few docs patches pushed.

decentral1se closed this issue

2024-07-07 10:29:40 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#587