Skip to content

Conversation

@twerthi
Copy link
Contributor

@twerthi twerthi commented Jan 29, 2026

Before submitting your PR, please delete everything above the line below.


Background

The instructions in the Parameter gave the example of #{Octopus.Action.Package[Template.Azure.Container.Image].PackageId}. In situations where there was an organization preceding the package name, ie. octopussamples/ocopub-frontend, the container name was being set to octopussamples/octopub-frontend. The / would cause issues and make the registration think it needed to be in a subfolder.

Results

The change updates the example from #{Octopus.Action.Package[Template.Azure.Container.Image].PackageId} to `#{Octopus.Action.Package[Template.Azure.Container.Image].PackageId | Replace "/" "-"}

Before

Setting the name to the example would result in step failure.

After

The character replacement results in a valid container name; octopussamples-octopub-frontend

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 # . If there is an open issue that this PR fixes add it here, otherwise just remove this line

@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

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.

1 participant