LetsEncrypt: Support for DNS alias in Azure

[farhanalam]

Background

Reference https://poshac.me/docs/v4/Guides/Using-DNS-Challenge-Aliases/

The setup:

• mydomain.com is highly locked down. Only account type that can be created here is of the admin types (not something I want a service account to use).
• myotherdomain.com DNS is hosted in Azure, and allows more granular permission control for service accounts.
• _acme-challenge.mydomain.com is an existing CNAME alias for thealias.myotherdomain.com

Results

Providing the DNS alias parameter as thealias.myotherdomain.com to POSH-Acme's New-PACertificate results in the acme challenge nonce getting written to the TXT record of thealias.myotherdomain.com and the verification of _acme-challenge.mydomain.com succeeds.

Before

--

After

Notice the alias for the .net domain is used but the challenge is for the .com one.

Pre-requisites

• Id should be a GUID that is not 00000000-0000-0000-0000-000000000000
  • NOTE If you are modifying an existing step template, please make sure that you do not modify the Id property (updating the Id will break the Library sync functionality in Octopus).
• Version should be incremented, otherwise the integration with Octopus won't update the step template correctly
• Parameter names should not start with $
• Step template parameter names (the ones declared in the JSON, not the script body) should be prefixed with a namespace so that they are less likely to clash with other user-defined variables in Octopus (see this issue). For example, use an abbreviated name of the step template or the category of the step template).
• LastModifiedBy field must be present, and (optionally) updated with the correct author
• The best practices documented here have been applied
• If a new Category has been created:
  • An image with the name {categoryname}.png must be present under the step-templates/logos folder
  • The switch in the humanize function in gulpfile.babel.js must have a case statement corresponding to it

[github-actions]

Start Hyponome locally

docker pull ghcr.io/hnrkndrssn/hyponome:main
docker run --rm -p 8000:8080 -it ghcr.io/hnrkndrssn/hyponome:main

Review in Hyponome

[hnrkndrssn]

Looks good to me 👍 Thanks for your contribution!