iis-website-add-release-number-to-response-header: Fix error #766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed the following exception
Credit for revealing the root cause (in some instances the script would load the incorrect assembly, which in turn would try to modify the incorrect configuration file):
dsccommunity/xPSDesiredStateConfiguration#191 (comment)
Credit for the solution:
dsccommunity/xPSDesiredStateConfiguration#462
Added a prefix to parameter names
Note that this may cause Octopus to prompt users who update the step in existing processes to do so manually.
Step template checklist
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 authorIf a newCategory
has been created:An image with the name{categoryname}.png
must be present under thestep-templates/logos
folderTheswitch
in thehumanize
function ingulpfile.babel.js
must have acase
statement corresponding to it