Skip to content

Conversation

@twerthi
Copy link
Contributor

@twerthi twerthi commented Jan 20, 2026


Background

Customer requested adding the check command option to the template.

Results

Added check to available commands to select within the template.

Before

This template did not have the option.

After

Option has been added and generated report is added as an Octopus Artifact.

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 #1643

@github-actions
Copy link

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

"DisplaySettings": {
"Octopus.ControlType": "Select",
"Octopus.SelectOptions": "prepare|Prepare\ndeploy|Deploy"
"Octopus.SelectOptions": "check|Check\ndeploy|Deploy\ndeploy|Deploy\nprepare|Prepare"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a duplicate deploy|Deploy here

Suggested change
"Octopus.SelectOptions": "check|Check\ndeploy|Deploy\ndeploy|Deploy\nprepare|Prepare"
"Octopus.SelectOptions": "check|Check\ndeploy|Deploy\nprepare|Prepare"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doh! Good catch, removed.

Copy link
Contributor

@bec-callow-oct bec-callow-oct left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good, just the minor duplicate value to fix per my other comment

@twerthi twerthi merged commit 8f3981b into master Jan 21, 2026
3 checks passed
@twerthi twerthi deleted the update-flyway-state branch January 21, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flyway State Based Migration should have Check Changes command added

2 participants