I upgraded to Octopus 3.0.16.2438 today and noticed problems with nested variables. Here is the scenario:
Variables
- Server/Name – configured as “production”
- WebsiteBinding – configured as “myapp-#{Server/Name}.mydomain.com”
In this scenario, the #{Server/Name} text does not get substituted with “production” as I would expect. Instead, when trying to set the IIS website bindings, the raw value of “myapp-#{Server/Name}.mydomain.com” is being used (unexpected). This worked fine in the latest Octopus 2.6 release.
If I change to just “ServerName”, everything starts working as expected, so it must be the forward slash that is causing the trouble.