Added step templates to support AMI Blue/Green deployments

[mcasperson]

Background

We have customers asking for an opinionated solution for Blue/Green deployments with AWS Auto Sclaing Groups. This PR adds 5 new steps that allow:

1. The online and offline target groups to be determined
2. The online and offline ASGs to be determined
3. Update a launch template with a new AMI
4. Initiate a instance refresh and wait for it to complete
5. Pointing all traffic to a new target group

Results

The steps can be combined in a deployment process to implement Blue/Green deployments with ASGs.

After

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

[harrisonmeister]

LGTM