Manually specify file type for Structured Configuration Variables feature

We are encountering a similar issue to the discussion in: Structured Configuration Variables for *.exe.config

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.

Hi @andrew3,

Thank you for contacting Octopus Support.

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.


Hey Donny,

Thanks for the quick reply. We will find another way.

Hi Donny,
specifying the file type would be really helpful. Has it been raised as a feature-request?


1 Like

Hi @john.enoksen,

Thank you for your question.

This is becoming a popular request. As such, a github issue was created to track this:

@andrew3, this would resolve your issue as well.

Feel free to subscribe to the github issue page to get notified as this gets worked on.

If anyone has any additional questions about this, please feel free to ask.


1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.