Update services that utilize ssh key authentication

[mikemimik]

Relates: #4

When the dotfiles scripts right and an ssh key is generated, it should be uploaded to all services that leverage ssh keys. If generating a new ssh key, distribute it to the list of services below.

Challenges:

1. making sure all services have programmatic access to add ssh keys
2. foundational access to the services will need to exist to even upload the ssh keys (provided they have programmatic access to add ssh keys)

Services List:

• github (version control)
• bitbucket (version control)
• digitalocean (infrastructure)
• hyper (infrastructure)
• heroku (infrastructure)
• algo (vpn)

[mikemimik]

Programmatic access of services:

• github
• bitbucket
• digitalocean
• heroku

[mikemimik]

Hyper uses a cli to interact with their service, which doesn't require an ssh key. It uses access_key/secret_key type creds to interface with the service.

[mikemimik]

Adding a new ssh key to algo isn't possible due to the immutable nature of the droplet. If you want a new ssh key, you need to blow up, and create a new droplet.

[mikemimik]

Hyper as a service is no longer available. They closed as of Jan 15, 2019

[mikemimik]

Github API:

reference

The following code snippet should add a new ssh key to a github account.

curl -u "user:pass" --data '{"title":"test-key","key":"'"$(cat ~/.ssh/id_rsa.pub)"'"}' https://api.github.com/user/keys