OctopusDeploy
Old Step Template names in a Space can be used on new Step Templates, but errors when the "Version" field in the JSON attempts to change from 0 to 1
Severity
Low, potential for larger impact on instances with high usage in individual Spaces
Version
Likely since 2018.X+
Latest Version
None
What happened?
Old Step Template names in a Space can be used on new Step Templates, but errors when the "Version" field in the JSON attempts to change from 0 to 1. This is a problem for several reasons:
- The error message makes no mention of the source ActionTemplate ID in conflict (the original Step Template that held the name in question)
- Even if you know the source ActionTemplate ID and wish to delete it, you must first remove the source Step Template from any deployment processes (and possibly delete associated Releases)
- Initially creating a Step Template with a name that falls into this scenario should not be possible
- Step Templates imports with a name that falls into this scenario should also not be possible
- You cannot change the name of a newly created Step Template affected by this. You must delete and recreate with a unique name.
- There is no visibility for what is effectively a blacklist of Step Template names
Likely due to: https://github.com/OctopusDeploy/Issues/issues/4001
Reproduction
- Create a Step Template called "Hello World"
- Make a change and save a few times to bump the current version number up
- Rename "Hello World" to "Hello World (old)"
- Create a new Step Template called "Hello World"
- Attempt to make any change after the initial save
Step Template creation example after initial save:
JSON:
Changes to Step Template:
Error:
Error and Stacktrace
No response
More Information
No response
Workaround
If you have created a new Step Template that is affected by this (unable to save after the initial save due to the name conflict), you can either:
- Recreate the Step Template from scratch with a new name
- Export the new Step Template -> Import -> change the value for the "Name" field -> Save
The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email [email protected]. Knowing how many people this issue affects helps us determine its priority.
