Settings and activity
3 results found
-
1 vote
David Gard
shared this idea
·
-
1 voteDavid Gard
shared this idea
·
-
43 votes
An error occurred while saving the comment David Gard
supported this idea
·
For me the issue is having to update code if a step name changes. On occasion, the person updating the Octopus process doesn't have access to the code, and another person has to become involved. It's also pretty easy to overlook having to update code when changing something in Octopus.
Personally I wouldn't be bothered by having to access an output variable using a GUID. We already have to use a GUID for setting variable values when deploying a release through the API, so there is precedent to use the GUID.
Is there any reason why `Set-OctopusVariable` can't output multiple output variables, giving the user the option to reference the output variable in the way that suits them?
1. Original -
$OctopusParameters["Octopus.Action[Step Name].Output.VariableName"]
2. Using step GUID -
$OctopusParameters["Octopus.ActionFromId[08c21caa-123f-4853-8b11-3797340ac977].Output.VariableName"]
3. As suggested by William Steinford -
$OctopusParameters["Octopus.Output.VariableName"]