Run ssh-keyscan, or regular SSH, during abra server add
#203
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
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#203
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, for anyone using an app config repo (e.g. Autonomic, or Neuronic), new users get a gnarly SSH error message when they try to run their first abra command, if they haven't SSH'd to that machine before.
We could avoid this by doing
ssh-keyscan
, or a regularSSH
connection, duringabra server add
(I think it's probably too heavy to do this before every remote Docker run, and we'd also need to add conditional checks to disable them for thedefault
context)Perhaps a
ssh-keyscan
when runningabra server add ...
will do it?