Thanks for getting in touch! Octopus’ built-in Configuration Transforms feature uses XML transformation to work, so unfortunately this won’t work for YML files. However you can use the Substitute Variables in Files feature which will allow you to substitute matching project variables into your YML (or any other text file) using the #{Variable} syntax. Would this feature work for your requirements?
Let me know what you think or if you have any further questions moving forward.
“Substitute Variables in Files” feature works for us with #{variable} syntax but we are wondering if you have any plans to implement the .yml feature configs transformations as well similar to json file transformations u currently have.
Thanks for getting in touch! Great to hear the standard variable substitution feature works, however there are no immediate plans to implement .yml specific config transformations, unfortunately. We’d love to continue gauging the community support behind this potential feature, so I’d suggest voting/commenting on this existing UserVoice item.