Support Output Variables for Offline Drop

[zentron]

A highly voted UserVoice request (324 votes) is to provide the same support for output variables for offline drops as exists for standard deployments.

Although the execution environment is somewhat different one approach has been suggested that sounds viable.

1. Intercept the output stream from each calamari step
2. Look for any output variable services messages
3. Decode the values and put them into an in-memory hashtable
4. When the next calamari step runs, take this hashtable and pass the variables in. This can be done with a new variables parameter that just takes a raw base64 encoded JSON representation that is combined inside calamari with the variables obtained through the standard variable files.

[zentron]

Resolved By: https://github.com/OctopusDeploy/OctopusDeploy/commit/1802cb20b2ff2065b143d49534e03eacca0de854

[warrenrumak]

Yeah! This makes me super happy. I'll try it out.

[zentron]

One limitation is that given how variables are replaced at the time they are written the #{} template format will not work, you will currently need to use the $OctopusParameters[] format to ensure that they pick up the required values

[warrenrumak]

So I tried it. So far so good.... but is there a specific reason why the Receive-Output function calls Write-Host $_ instead of just passing through the input, i.e. Write-Output $_ ?

I'm asking because this is effectively a behaviour change from prior to 2018.3.8....

[zentron]

Was there a reason? Does oversight count? A fix will be provided in the next release to use Write-Output instead
#4490

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.