I am trying to use a variable to determine whether or not an IIS Binding is enabled or disabled. Ultimately, I want to use an if expression. However, I am having an issue that even if my custom expression is simply a variable representing true or false and error is thrown. I have attached the IIS Binding, variable setup, log showing the variable values, and the error message.
Thanks for reaching out! I just tested this really quick in 3.10.0 and it worked as expected on my end.
Could you please follow the instructions on the below doc and send me a full deployment log? That should help me figure out what’s going on on your end.
The problem here seems to be the binding with the && logic on it, which is not something we support at the moment. The only way to currently fake the && logic for variable replacement is by using nested IF statements like #{if var1}{if var2}true{/if}{/if}#
The other variable with the single #{True} variable looks ok. I tested it on my end and it looks exactly like yours in the log:
07:29:20 Verbose | [Octopus.Action[Deploy test website].IISWebSite.Bindings] = '[{"protocol":"http","ipAddress":"*","port":80,"host":"","thumbprint":"","requireSni":false,"enabled":true},{"protocol":"http","ipAddress":"*","port":"81","host":"","thumbprint":"","requireSni":false,"enabled":"#{True}"}]'
Sorry I took some extra time to get back to you for this. It took me a fair amount of re-learning this feature that I haven’t used in a while :). In the meantime I even found a bug which made almost made me lose my mind for 2 straight hours: https://github.com/OctopusDeploy/Issues/issues/3200
Another pro tip that I learned the hard way today is that the comparison value (what comes after the ==) is ultra case sensitive. So build-server is not the same as Build-Server and Local is not the same as local.
Looks like your message didn’t come in full. Sad to see those errors still there :(.
Is there any chance you can create a brand new test project and instead of using those 4-5 bindings all at once, try them one at a time so we can get the smallest possible way to reproduce this error.
Once you do that send me the same log with debug variables on from the clone project.
Set the custom expression of your IIS binding “enabled” field to just the single variable you created on the pre-deploy script(*). In my example that would be #{MyBindingVariable} (see attached screenshot)
Notes about the script:
In this line you’ll be setting the name of the variable that you’ll use in your binding’s “Enabled” field
These 2 lines set the conditonal logic for the variable.
