In a manual intervention step, I can scope it per environment. I don’t see a way to do this for a NuGet package deploy step.
The reason is that we have a ClickOnce deployment packaged for each environment. ClickOnce hashes the contents and validates the hash at download time, so we can’t have Octopus modify config files. So, what I really need is a way to scope each ClickOnce package just for its own environment. Is there a way to do this?