Allow updating of existing Step Templates via the Import feature
The ability to import step templates from other locations (e.g. Octopus Library) is awesome, but if someone updates the step template the import process can not be used to update the copy I have in my Octopus server. I'm forced to delete the step template and re-import it. Obviously if I have N projects that rely on the step template I'm now stuck because I can't delete it when projects are using it.
Since I can technically update the powershell script and change parameters and so on inside of Octopus Deploy UI itself, importing of existing step templates should just offer to do the same thing and update the pieces for me.
Drew Marsh
shared this idea
Thanks for voting on this suggestion. We’re working on a number of changes to the step template library, and this is one of them. It should ship in the next month or so.
2 comments
-
Tim
commented
did this happen?
-
fiona.gazeley@red-gate.com
commented
As a developer of step templates our changes often involve adding new parameters (to expose new functionality in the template). Currently there isn't a nice way of getting these new templates to our users. Ideally I'd like users to be able to overwrite the whole template (not just the script part).