Fixing an issue in the run a runbook step when a fixed version of a package is used

[BobJWalker]

Background

This PR fixed Issue 1680 - when a fixed version of a package is used in a runbook it causes a 400 bad request when attempting to run a runbook.

This happens when:

• Unpublished runbook is allowed or when using a version controlled runbook.
• The package version is fixed in a runbook step
• There is a newer version of that package

The reason this happens is because the step was always attempting to find the latest version of the package.

Results

This fixes the issue:

• Works when a package version is fixed
• Works when a package version is not fixed (always use latest)

Before

When the package version was fixed:

It would still attempt to use the latest version:

After

After this update that error no longer occurs:

Also verified that this works when not specifying a package version (regression testing)

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

Fixes #1680

[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