Posts

After the 4th or 5th time the https://0to1.nl domain hosting company got taken over, the interface seemed to get worse and worse, I decided to move the domain to TransIP. I worked with the TransIP interface before and it is easy to manage, they offer an API and 2FA so my requirements were quickly met.

Every couple of months I register a domain for a project I plan to work on. The end result is hundreds of euros in costs per year for domains I hardly use. Today was going to be different! I registered https://imkerijsoest.nl for my beekeeping hobby and after struggling with setting up Let’s Encrypt on TransIP I was reminded why I registered this domain: To document these steps and share them with the world.

This HOWTO will very likely be out of date soon, since Microsoft updates their Azure portal way too often to make documentation reliable. The official documentation for setting up OpenID in Azure Active Directory was outdated and I could not find a few of the listed options they described on: https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/configure-openid-settings. If this documentation can help one or two people with setting this up it would be worth it, since i spend a couple hours on finding the right endpoints and setup i decided to make this HOWTO. In this HOWTO we are going to set up OpenID for DCOS Enterprise. Currently this is all text, since I only have access to Azure through my employer and I do not want to share any details from their accounts.

A couple days ago I was reading questions on a tech website, in one of the topics someone explained an issue that they needed to copy from an SFTP location files in a cron job. They tried using rsync, however SFTP does not support interactive sessions which rsync sets up. As a solution I mentioned rclone. This is such a great tool that has been in my arsenal for quite a while now and I thought it would be good to give a shoutout to this tool.

While sharing the solution to issues you encountered is great, sometimes tools are worth mentioning even if you did not build them or have issues with them. Most of the IT staff would not be where they are now without good tooling, this post is to add praise to one of those tools. Perhaps I will do this more often, but first lets discuss: Shellcheck.

Since a couple years I have incorporated Shellcheck in my daily bash shell script writing. It has greatly improved my scripts, made them more readable and the result is clean code without any nasty surprises. Shellcheck gives sane feedback to your scripts, provides best practices and reports syntax issues. The result is uniform and clean scripts that are readable. The best feature about Shellcheck is that if you made an error, it will point you to the SC code that can be looked up on the wiki of the shellcheck repo: https://github.com/koalaman/shellcheck

The terraform module change I deployed seemed to have valid syntax, the module initialized properly with terraform init. The terraform plan created a valid plan, no errors or syntax issues were raised. When I started to execute the plan with terraform deploy it returned the following error:

Error: Error launching source instance: VPCIdNotSpecified: No default VPC for this user
        status code: 400, request id: xxx

This error pointed me towards a bug report on the Terraform github issues page, this stated:

package main

import "fmt"

func main() {
    fmt.Println("hello world")
}

Hello world!