Using values file to handle simple variable replacement is cool. It's painful to do that for multiline texts defined as Octopus Variable. It's very hard to get the indentation right. A somehow easier way will be using ".Files.Get" and then pipe to "nindent". This means we have a text file in which the variables are to be substituted during the same step like "Upgrade Helm Chart" and that file is not a helm values file at all.

"Upgrade Helm Chart" already has a feature "Custom Deployment Scripts", which can be used to do this. But a much more easier way will be to add another optional feature "Substitute Variables in Templates" (as available to "Deploy a Package" step) to the step. This will make the deployment much cleaner.

What is the downside of adding an optional feature "Substitute Variables in Templates" to all the steps in general?