Pass variables from one step to another
As a package author, I'd like to be able to return variables from my PowerShell scripts in one deployment step, and have them passed to the next deployment step as inputs, so that I can pass useful context information from one step to another.
This has shipped; results of Set-OctopusVariable will be carried through to subsequent steps as Octopus.Actionname_].Outputmachine_].variable.
Leblanc Meneses commented
Since a package could be ran on multiple machines - which machine value would you keep? Where would this feature be used?
Would not each package be self contained? - the only dependency is that the previous steps have executed successfully.