Can't scope NuGet package deploy

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?

Looks like I can accomplish this with roles. I can create a role for that server in each environment, so only that environment’s package would be deployed.

Would that be the recommended approach?

Hi Jack,

That’s right, roles were designed for this. But we’ll probably add environment scoping to package steps in a future release too.