Skip to content

Conversation

@twerthi
Copy link
Contributor

@twerthi twerthi commented Apr 21, 2025


Background

The original code was incorrect and would only select deployments that were in an Executing state. This worked for deployments in Guided Failure mode, however, did not work for Manual Intervention steps. I've fixed the code so it makes the correct API call passing in the state for the type of intervention the user wants to automate the response for.

Results

The template now correctly retrieves the Tasks so that it can perform the automation of submitting the selected response.

Before

When attempting to use the template for Manual Intervention the API call would not return any results and therefor it would not automate the submission.

After

The template now provides the correct value to filter by depending on what the user has selected within the template.

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

@twerthi twerthi merged commit caadef5 into master Apr 22, 2025
3 checks passed
@twerthi twerthi deleted the update-automate-response branch April 22, 2025 23:44
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.

2 participants