Hetzner provider.

[Johannestegner]

Description

This pull request contains code which allows for provisioning of the cheapest server type at Hetzner cloud to be used as an inlet end node.

I made the default region hel1 (Helsinki, Finland) and the server type is the cx11 (€2.49/month) with Ubuntu 20.04.

This should close #67 if accepted.

How Has This Been Tested?

I tested the provider manually multiple times on Windows 10 Pro and on Ubuntu 18.04 (via WSL2).
The following steps was taken:

1. Docker container with nginx was set up with port 8000 exposed.
2. Inletctl was ran with the new provider and available flags, using access token from Hetzner web interface.
3. Visited the IP of the hertzner provisioned machine, which showed the correct nginx startup screen.
4. Closed the docker container.
5. Visited the IP of the hertzner provisioned machine, which no longer shows the nginx startup screen.
6. Ran delete command and verified that the machine was in fact removed.

---

Edit after testing with latest commits:

Used the same procedure as above, with all available regions, with same successful result.

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

No changes, only a new provider added.

Checklist:

I have:

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

[alexellis]

Hi @Johannestegner thanks for the PR - it will be nice to have Hetzner available as an option for inlets users.

@zechenbit would you be able to review this patch please?

Alex

[alexellis]

@Johannestegner could you test with inlets PRO?

Here's a license you can use:

Name:	Johannes Tegnér
Email:	johannes@jitesoft.com
Expires in: 3 days, on: 25 July 2020
Products: [inlets-pro]

Note: use text under the line
---
eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiSm9oYW5uZXMgVGVnbsOpciIsImVtYWlsX2FkZHJlc3MiOiJqb2hhbm5lc0BqaXRlc29mdC5jb20iLCJwcm9kdWN0cyI6WyJpbmxldHMtcHJvIl0sImF1ZCI6Imp3dC1saWNlbnNlIiwiZXhwIjoxNTk1Njk2NDM4LCJqdGkiOiI4MDgxIiwiaWF0IjoxNTk1NDM3MjM4LCJpc3MiOiJqd3QtbGljZW5zZSIsInN1YiI6IkpvaGFubmVzIFRlZ27DqXIifQ.V_7iUi6nVL1v2sHaDz2uMJ3urXLbqtrnnj4ctfQHIzcFCFdX1dubG7vyYmL4elejAjX7KxDp6q0UxIiC3LKjCQ

The way to switch is to use --remote-tcp and a machine to proxy all ports to, 127.0.0.1 is useful for things running on your computer.

[alexellis]

Please also update this file -> https://github.com/inlets/inletsctl/blob/master/pkg/provision/README.md

[Johannestegner]

Will do! Just finishing off dinner real quick :)

[Johannestegner]

@alexellis took me a bit to figure out that I was using the wrong IP address of my local machine.... but when that was done, I could publish multiple services via the end node, so seems to work fine :)
Made a small fix to an uncaught error too which I will push up with the README file :)

[alexellis]

@Johannestegner please take a look at the feedback by @zechenbit and if there is an Ubuntu 16.04 image, let's use that for consistency please?

[Johannestegner]

@alexellis @zechenbit sending kids off with their grandma, then I'll take care of this :)

[alexellis]

Thank you, it would be great to get this released before Friday end of play, so that I can include it in the Insiders Update for this week.

[alexellis]

Could you update "How Has This Been Tested?" with your results from re-testing with the new commits? 👍 thank you for the quick turn-around

[alexellis]

Approved

[Johannestegner]

@alexellis Will do! Give me a couple of minutes :)

[Johannestegner]

Could you update "How Has This Been Tested?" with your results from re-testing with the new commits? 👍 thank you for the quick turn-around

Worked just as well, I added a small comment, if you want me to show some logs or similar I will gladly add them too :)

[Johannestegner]

Thank you guys! Was fun to write some Go for a change! :D