Add flag to aid in debugging abra server add #587
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#587
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?
Recently a new
abra
user asked for support in #coopcloud-tech to debug why they could not successfully complete theabra 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 theadd
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 whatabra
is intending to do in human friendly language such as which user, domain, ssh opts etc. Other names for this flag could be:Alternatively
abra
could just show this information at start of--debug
command