Add HTTPS tunnel support for create command

Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com

Description

This enables fast HTTPS tunnels to be provisioned.

How Has This Been Tested?

Tested with the staging issuer and a custom domain. This relies on a new service file, which will be published with each new inlets PRO binary release.

inlets-pro-http.service is fetched and the defaults file is populated with the Let's Encrypt data such as domain, email and issuer.

mkdir -p $GOPATH/src/github.com/inlets/
cd $GOPATH/src/github.com/inlets/
git clone https://github.com/inlets/inletsctl --branch=https-tunnels
cd inletsctl

# Change to "prod" or remove `--letsencrypt-issuer` to use the default
export ISSUER=staging

go build && ./inletsctl create \
  --letsencrypt-domain site1.alex.o6s.io \
  --letsencrypt-email contact@o6s.io \
  --letsencrypt-issuer staging \
  --access-token-file ~/.secrets/access-token

I've tested staging, I'd like someone else to leave that flag off, which should default to prod.

I then ran: doctl compute domain create site1.alex.o6s.io --ip-address 138.68.190.75 as fast as I could.

I connected a PythonSimpleHTTP server to the tunnel with the printed-out client command from inletsctl

staging-cert

How are existing users impacted? What migration steps/scripts do we need?

Create will always provision TCP tunnels, unless the --letsencrypt-* flags are given.

Checklist:

I have:

[ ] updated the documentation and/or roadmap (if required)
[x] read the CONTRIBUTION guide
[x] signed-off my commits with git commit -s
[x] added unit tests

inlets / inletsctl