Adding new template for checking argo cd instance existance

[twerthi]

---

Background

This template checks to see if there are any Argo CD instances registered to the Octopus Deploy server. This template was created in support of our Octopus AI Assistant for converting Samples projects into things customers can easily implement on their instance.

Results

Informs the user if there is an instance, points to our documentation if there isn't.

Before

There was nothing before, the world was a bleak, meaningless existence.

After

Knowing that you do or do not have an Argo instance connected to your Octopus instance has a profound effect on the psyche. No more guesswork, no more clicking, just glorious knowledge.

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