Open sudo-jtcsec opened 1 year ago
Just recently ran into this, but also think it might be good to only create new sshconfig for droplets that have been created by axiom. I worked around this by creating a new "instances_axiom()" function in do-functions.sh. I'll try and submit a PR.
After spinning up a new DO fleet, I kept getting sshconfig errors when launching scans such as below:
Looking at my .axiom/.sshconfig file, I found an entry was scuffed:
The issue persisted after I fixed the config file manually - Im assuming its checked in the background and will repush the bad config.
More investigation shows that for a DO droplet not in my fleet I configured a reserved IP, which I believe is being returned in a query for VM IPs as an unexpected additional entry, which then breaks the sshconfig generation.