We have an XML file that we would like to use the Structured Configuration Variables feature for, but it doesn’t have a *.xml file extension. In our specific case it is an NLog.config file that we are trying to modify as part of a .NET deployment (either as an IIS website or as a Windows Service). Is there no way to manually specify the file type of a file using the Structured Configuration Variables feature?
The Structured Configuration Variables does everything we need, just the lack of flexibility in the file names it will accept is preventing us from using it it seems.
There isn’t a workaround at this time as the Structured Configuration Variables feature detects the file type based on extension only for XML files. The only way to get this to work would be to present Octopus with a file ending in .XML.
The only other option we can offer would be to use the Substitute Variables in Templates feature. However, this means a completely different approach and sounds like a poor solution in this situation.
I wish I had a better answer for you. Please don’t hesitate to reach out if you have any more questions about this or anything else.