It’s Friday morning and you’re about to wrap early on your weekly development sprint. The PR uses a new browser feature, so there’s one thing left to do before merging: test it with HTTPS. You ask Google how to get a certificate for development, and they point you to the stackoverflow article aptly titled “how to get a localhost certificate”. Only one cryptic incantation of openssl command line flags stands between you and an early weekend:
If you have found yourself manually provisioning certificates this way it’s likely because you were trying to accomplish another goal altogether, such as:
Chances are your company uses an ACME powered certificate authority in your staging and production environments, so provisioning certificates for your public domain isn’t something you’ve even thought about. But what about in development? And how about for your backend services?