This PR defines a step that can be used to export a single runbook.
Results
Pre-requisites
[x] 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).
[x] Version should be incremented, otherwise the integration with Octopus won't update the step template correctly
[x] Parameter names should not start with $
[x] 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).
[x] LastModifiedBy field must be present, and (optionally) updated with the correct author
[x] If a new Category has been created:
[x] An image with the name {categoryname}.png must be present under the step-templates/logos folder
[x] 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
Background
This PR defines a step that can be used to export a single runbook.
Results
Pre-requisites
Id
should be a GUID that is not00000000-0000-0000-0000-000000000000
Id
property (updating theId
will break the Library sync functionality in Octopus).Version
should be incremented, otherwise the integration with Octopus won't update the step template correctly$
LastModifiedBy
field must be present, and (optionally) updated with the correct authorCategory
has been created:{categoryname}.png
must be present under thestep-templates/logos
folderswitch
in thehumanize
function ingulpfile.babel.js
must have acase
statement corresponding to itFixes # . If there is an open issue that this PR fixes add it here, otherwise just remove this line