I was trying to use the JSON Configuration variables feature in the Deploy Site process - and could not get it to work.
Very simple situation, I wanted a file to be available on my resulting site to contain the a build value (set before reaching Octopus) and then the Octopus release number. This would allow a developer or devops to simply check this file and know that both build and release had refereshed the site (even when there were no visual changes).
So the JSON file was simply:
I wanted the second value with the Release Id - no combination of varible name or scope could get the file to contain anything except the “”. I know that the json file was detected because entering an incorrect path showed as an error in the deploy site step.
There were a few comments on other questions, but they generally end up with "you could (some even implied you should) use the “Substitue Variables in Files” option instead.
Am I missing something obvious?