Hi. I love the idea of the “deploy a release” step template, and would like to use it to manage multi-component projects. If the deployment step is actually run, you can of course access output variables from it (e.g. package locations)…
However, I’m at a loss as to how to find package locations for later use if you use a deployment condition which does not result in the release being deployed (i.e. if you select “If the selected release is not the current release in the environment” or “If the selected release has a higher version than the current release in the environment”)
Ideally, the variables from the release that Octopus has found as having been already deployed, would be made available to the calling release in place of those that would normally be made available.
Or am I missing something…?