Ssh Aliases Save

A tool for ~/.ssh/config generation

Project README

ssh-aliases

Build Status Go Report Card

ssh-aliases is a command line tool that brings ease to living with ~/.ssh/config.

In short, ssh-aliases:

  • combines multiple human friendly config files into a single ssh config file
  • is able to generate a list of hosts out of a single entry by using expanding expressions, like instance[1..3].example.com or [master|slave].example.com
  • is able to generate aliases for provided (as an input file) lists of hosts using regular expressions matching
  • creates aliases for hosts by compiling templates
  • allows multiple hosts reuse the same ssh configuration
  • is a single binary file

Table of contents

Installation

Binary distribution

Binary releases for Linux and MacOS can be found on GitHub releases page.

Homebrew tap

MacOS users can install ssh-aliases easily using Homebrew:

brew tap dankraw/ssh-aliases
brew install ssh-aliases

Source code

If you are familiar with Go:

go get github.com/dankraw/ssh-aliases

There is a Makefile, so you can use it as well:

make test # run tests
make fmt  # format code
make lint # run linters
make      # build binary to ./target/ssh-aliases

Configuration files

ssh-aliases is a tool for ~/.ssh/config file generation. The input for ssh-aliases are HCL config files. HCL was designed to be written and modified by humans. In some way it is similar to JSON, but is more expressive and concise at the same time, allows using comments, etc.

Looking at examples below will be enough to become familiar with HCL format.

Scanned directories

ssh-aliases allows you to divide your ssh configuration into multiple files depending on your needs. When running ssh-aliases you point it to a directory (by default it's ~/.ssh_aliases) containing any number of HCL config files. The directory will be scanned for files with .hcl extension. Keep in mind it does not scan recursively - child directories won't be considered.

Components

A single config file may contain any number of components defined in it. Currently there are three types of components:

Host definitions

A host definition consists of a host keyword and it's globally unique (among all scanned files) name. Each host should contain following attributes:

An example host definition looks like:

host "my-service" {
  hostname = "instance[1..2].my-service.example.com",
  alias = "myservice{#1}"
  config = {
    user = "ubuntu"
    identity_file = "~/.ssh/my_service.pem"
    port = 22
    // etc.
  }
}

or (when pointing an external config named my-service-config)

host "my-service" {
  hostname = "instance[1..2].my-service.example.com",
  alias = "myservice{#1}"
  config = "my-service-config"
}

or (when using regular expression to match selected hosts from user input)

host "my-service" {
  hostname = "instance\\-(\\d+)\\.my\\-service\\-([a-z]+)\\..+dc1.+",
  alias = "{#2}.myservice{#1}.dc1"
  config = "my-service-config"
}

Config properties

A config properties definition consists of a config keyword and it's globally unique (among all scanned files) name. It's body is a list of properties that map to ssh_config keywords and their values. A complete list of ssh config keywords can be seen here or listed via man ssh_config in your terminal.

Each property may contain an underscore (_) in its keyword for clarity, all underscores are removed during config compilation, first character and all letters that follow underscores are capitalized - this makes generated file easier to read. For example, identity_file will become IdentityFile in the destination config file. By design ssh_config keywords are case insensitive, and their values are case sensitive.

Provided properties are not validated by ssh-aliases, so it should work even if you have a custom built ssh command.

An example config properties definition may look like:

config "some-config" {
  user = "ubuntu"
  identity_file = "id_rsa.pem"
  port = 22
  // etc.
}
Extending configurations

A special property _extend can be used in order to include properties from other configurations. Top level properties override lower level properties.

config "top-level" {
  user = "eden"
  _extend = "lower-level"
  # port = 2222 (will be included from below configuration)
  # ...
}

config "lower-level" {
  user = "helix"
  port = 2222
  # etc.
}

A single configuration may extend multiple configurations, in this case an array of configuration names should be provided as the _extend property.

config "top-level" {
  user = "eden"
  _extend = ["lower-level1", "lower-level2"] 
  # configurations are included from left to right (and overridden in this order)
  # port = 4444
}

config "lower-level1" {
  user = "helix"
  port = 2222
  # etc.
}

config "lower-level2" {
  user = "torus"
  port = 4444
  # etc.
}

Variables

Variables are declared in object blocks marked with var keyword. There may be many var blocks distributed along multiple files, but variable names have global scope, so each one can be declared only once.

Example variables block may look like:

var {
    dc1 = "my.domain1.example.com"
    dc2 = "some.other.domain2.net"
    keys {
        service_a = "/path/to/a_key.pem"
        service_b = "/path/to/b_key.pem"
    }
    nodes {
      service_a = 5
    }
    users {
      a = "eden"
      b = "helix"
    }
}

Variables can be nested, their lookup names are flattened during processing with . separator. In this example we have defined following variables: dc1, dc2, keys.service_a, keys.service_b, nodes.service_a, users.a, users.b.

Variables can be used in:

  • Aliases
  • Hostnames
  • Config property values

String interpolation with variables is done by using a ${name} placeholder, for example:

host "service-a" {
  hostname = "instance[1..${nodes.service_a}].${dc1}",
  alias = "myservice{#1}"
  config = {
    user = "${users.a}"
    identity_file = "${keys.service_a}"
  }
}

Expanding hosts

One of the most important features of ssh-aliases is hosts expansion. It's a mechanism of generating multiple Host ... entries in the destination ssh_config out of a single host definition. It is done by using expanding expressions in hostnames and compiling host aliases from templates.

Expanding expressions

There are two types of expanding expressions available:

  • ranges
  • sets

A range is represented as [m..n], where m and n are positive integers that m < n. For example, a hostname instance[1..3].example.com will be expanded to:

instance1.example.com
instance2.example.com
instance3.example.com

A set is represented as [a], [a|b], [a|b|c] and so on, where a, b, c... are some arbitrary strings of characters allowed in hostnames. For example, a hostname server.[dev|test|prod].example.com will be expanded to:

server.dev.example.com
server.test.example.com
server.prod.example.com

Of course ranges and sets can be used together multiple times each. A final result will be a cartesian product of all expanding expressions provided. For example, a hostname server[1..2].[dev|test].example.com would be expanded to:

server1.dev.example.com
server1.test.example.com
server2.dev.example.com
server2.test.example.com

Alias templates

Each generated Host ... entry needs to have an alias that is provided in host definition. If hostnames are expanded it is required to provide placeholders for all expanding expressions used. Otherwise ssh-aliases would generate the same alias for multiple hostnames, and that simply makes no sense.

An expanding expression placeholder is represented as {#n}, where n=1,2...k, n points the n-th expression used in hostname (sequence from left to right) and so k is the number of expanding expressions used in total.

For example, {#1} points the first expression used in hostname, {#2} points the second, and so on.

If we look at the hostname example from above section server[1..2].[dev|test].example.com, we have two expressions used:

  1. [1..2]
  2. [dev|test]

We can declare an alias template like {#2}.server{#1}, which would compile following aliases for the generated hostnames:

dev.server1
test.server1
dev.server2
test.server2

Using regular expressions to match existing hostnames

Alternatively, instead of defining expanding expressions by hand, user can provide a list of existing hosts as an input file and define regular expressions that match selected groups of hosts, ssh-aliases will generate aliases and hook proper configurations to matched hosts.

For example, the user is able to fetch from some kind of cloud service API or an asset management system (or will just cat ~/.ssh/known_hosts | cut -f 1 -d ',' | cut -f 1 -d ' ') a list of nodes that is allowed to log into:

instance1.my-service-evo.example.com
instance1.my-service-dev.example.com
instance1.my-service-test.example.com
instance2.my-service-test.example.com
instance1.my-service-prod.example.com
instance2.my-service-prod.example.com
instance3.my-service-prod.example.com

If there are patterns existing between some of these hosts, a regular expression can be defined to match them, in this case "instance(\\d+)\\.my\\-service\\-(dev|prod|test)\\..+". Note there are two groups being captured (\\d+) for instance number and (dev|prod|test) for host environment (we want to omit the experimental evo environment). In order to place the captured group value into the alias use the {#n} placeholder, same as for expanding expressions.

Host definitions with a hostname containing at least a single group capturing statement (starting with a "(" parenthesis) are considered as regexp hosts type, and expanding expressions are not applied to them. Of course, both types of hosts can be mixed in the same ssh-aliases configuration (file or directory).

host "dc1-services" {
  hostname = "instance(\\d+)\\.my\\-service\\-(dev|prod|test)\\..+"
  alias = "host{#1}.{#2}"
  config {
    user = "abc"
    identity_file = "~/.ssh/key.pem"
  }
}

Compiling the aliases with --hosts-file /path/to/hosts_file.txt option will generate:

Host host1.dev
     HostName instance1.my-service-dev.example.com
     IdentityFile ~/.ssh/key.pem
     User abc

Host host1.test
     HostName instance1.my-service-test.example.com
     IdentityFile ~/.ssh/key.pem
     User abc

Host host2.test
     HostName instance2.my-service-test.example.com
     IdentityFile ~/.ssh/key.pem
     User abc

Host host1.prod
     HostName instance1.my-service-prod.example.com
     IdentityFile ~/.ssh/key.pem
     User abc

Host host2.prod
     HostName instance2.my-service-prod.example.com
     IdentityFile ~/.ssh/key.pem
     User abc

Host host3.prod
     HostName instance3.my-service-prod.example.com
     IdentityFile ~/.ssh/key.pem
     User abc

Printing the list of aliases accordingly would print:

config.hcl (1):

 dc1-services (6):
  host1.dev: instance1.my-service-dev.example.com
  host1.test: instance1.my-service-test.example.com
  host2.test: instance2.my-service-test.example.com
  host1.prod: instance1.my-service-prod.example.com
  host2.prod: instance2.my-service-prod.example.com
  host3.prod: instance3.my-service-prod.example.com

Tips and tricks

  • Generated ssh_config configuration can be used not only with ssh command, but with other OpenSSH client commands, like scp and sftp
  • Multiple alias templates may be provided for the same host definition, for example:
host "my-service" {
  hostname = "instance[1..2].myservice.example.com",
  alias = "myservice{#1} ms{#1}" # separated with space
  config = "some-config"
}
  • ssh_config (v7.2+) ships with Include directive (see docs) that can be used to include other files. This can be useful for mixing ssh-aliases generated configs with pure ssh_config files:
Include path/to/ssh-aliases/generated/ssh_config

# below some legacy ssh config that one day may be migrated to ssh-aliases
Host myservice
    HostName myservice.example.com
    User myself
# ...
  • config properties are optional when alias is provided:
host "example" {
    hostname = "my.service[1..2].example.com"
    alias = "myservice{#1}"
}
  • alias (or hostname when alias is provided) is optional when config properties are provided. This can be useful for creating wildcard (*) configurations that match any host:
host "all-hosts" {
    hostname = "*" # or alias = "*"
    config {
        # ...
    }
}

Usage (CLI)

Run ssh-aliases --help to see available options of the ssh-aliases command line interface (CLI).

In general, there are only two commands available:

  • compile - prints (or saves to a file) compiled ssh config
  • list - prints preview of generates aliases and hostnames

Both commands share the same global option: --scan or -s which should point to the directory containing input config files. If omitted, ssh-aliases will look for ~/.ssh_aliases directory. This option should be passed before the selected command name.

compile - generating configuration for ssh

compile is the primary command in ssh-aliases - it combines together all input config files and compiles configuration for ssh.

Options for compile

  • --hosts-file - input hosts file for regexp compilation (each hostname in new line)
  • --save - adding this option makes ssh-aliases save the output to the file instead of printing to stdout, asks for confirmation if the file exists (unless --force is used) and overwrites its contents if accepted
  • --file <PATH> - when using --save it tells where should the file be saved, defaults to ~/.ssh/config
  • --force - when using --save it will overwrite possibly existing file without confirmation
  • --help - shows command usage

Example command run with all options provided:

$ ssh-aliases --scan ~/my_custom_dir compile --save --file ~/.ssh/ssh_aliases_config --force

Now, let's suppose we have ./examples/readme directory that contains 3 files:

# ./example/readme/example_service_1.hcl
host "abc" {
  hostname = "node[1..2].abc.[dev|test].example.com"
  alias = "{#2}.abc{#1}"
  config = "abc-config"
}

config "abc-config" {
  user = "ubuntu"
  identity_file = "${keys.abc}"
  port = 22
}

# ./example/readme/example_service_2.hcl
host "other" {
  hostname = "other[1..2].example.com"
  alias = "other{#1}"
  config {
    user = "lurker"
    identity_file = "${keys.other}"
    port = 22
  }
}

# ./example/readme/variables.hcl
var {
    keys {
        abc = "~/.ssh/abc.pem"
        other = "~/.ssh/other.pem"
    }
}

Let's run compile command for that directory:

$ ssh-aliases --scan ./examples/readme compile

ssh-aliases will print:

Host dev.abc1
     HostName node1.abc.dev.example.com
     IdentityFile ~/.ssh/abc.pem
     Port 22
     User ubuntu

Host dev.abc2
     HostName node2.abc.dev.example.com
     IdentityFile ~/.ssh/abc.pem
     Port 22
     User ubuntu

Host test.abc1
     HostName node1.abc.test.example.com
     IdentityFile ~/.ssh/abc.pem
     Port 22
     User ubuntu

Host test.abc2
     HostName node2.abc.test.example.com
     IdentityFile ~/.ssh/abc.pem
     Port 22
     User ubuntu

Host other1
     HostName other1.example.com
     IdentityFile ~/.ssh/other.pem
     Port 22
     User lurker

Host other2
     HostName other2.example.com
     IdentityFile ~/.ssh/other.pem
     Port 22
     User lurker

list - listing aliases definitions

list command should be used to check correctness of declared hostname patterns and alias templates. It will print a concise list of compiled results, yet omitting linked config properties.

Options for list

  • --hosts-file - input hosts file for regexp compilation (each hostname in new line)

For example, let's run list for ./examples/readme directory from previous paragraph:

$ ssh-aliases --scan ./examples/readme list

The printed result will be:

readme/example_service_1.hcl (1):

 abc (4):
  dev.abc1: node1.abc.dev.example.com
  dev.abc2: node2.abc.dev.example.com
  test.abc1: node1.abc.test.example.com
  test.abc2: node2.abc.test.example.com

readme/example_service_2.hcl (1):

 other (2):
  other1: other1.example.com
  other2: other2.example.com

License

ssh-aliases is published under MIT License.

Open Source Agenda is not affiliated with "Ssh Aliases" Project. README Source: dankraw/ssh-aliases
Stars
49
Open Issues
2
Last Commit
4 years ago
Repository
dankraw/ssh-aliases
License
MIT
Tags
Golang Hcl Ssh Ssh Config

Open Source Agenda Badge

Open Source Agenda Rating
Submit Review Review Your Favorite Project
Submit Resource Articles, Courses, Videos
Submit Article Submit a post to our blog

From the blog

Dec 11, 2022

How to Choose Which Programming Language to Learn First?

From the blog

Dec 11, 2022

How to Choose Which Programming Language to Learn First?