Story #3193

Updated by Tom Clegg about 6 years ago

One page, four content areas (3 small "view only" plus one that lets you add/remove SSH keys)

* VMs I can log in to: show hostname, login name, last login (if available)
** Note about "See "setting up
available), SSH access" first"? config snippet
* Repositories I can access: name, is_writable, fetch or push-url (depending on whether it is writable)
** Note about "See "setting up SSH access" first"?
* Current API token
** Button to "show current token"
** Open a modal with the copy-and-paste section (currently shown on the Help tab of the "manage API tokens" page)

Manage SSH keys:
* Show my existing SSH keys (filter by key_type=="SSH")
* Delete existing SSH key (confirm with javascript)
* If no existing SSH keys, explain why you should add one (in order to access shell VM and repository)
* "Add SSH key" button
** modal with form, like "setup user"
** always set key_type to SSH
** error handling is important (many people will upload bogus keys!)
* "Setting up SSH access" section with the information that currently appears at @virtual_machines#index@

In each section, a "Learn more" link opens a new tab with the appropriate page of

Update nav links:
* Add "Account settings" item, in the email address dropdown, linking to this new page
* Make generic "show VMs, authorized_keys, API tokens" links show up only for admins, in the gear menu (like the Users item is now)
* If this means the gear menu is now empty for non-admins, then don't even show the gear menu for non-admin users!

Other notes:
* filter by owner_uuid == current_user.uuid so this page works nicely for admins too

|API tokens|/3. SSH keys|

|Virtual machines|