File encoding being set to UTF-8 BOM despite encoding option being set

[tothegills]

For variable transforms, the file encoding is being forced to UTF-8 BOM and seems to be ignoring the option to use template encoding.
See:
https://secure.helpscout.net/conversation/118999769/1448/

[tothegills]

This is happening post 3.0.10 (when a fix was made)

[Dalmirog-zz]

Possibly related https://secure.helpscout.net/conversation/120274077/1571/ ?

[DamianMac]

https://octopus.com/company/roadmap/why-was-this-closed

[TrentScholl]

Since it seems this won't be fixed.. If anyone comes across this, the work around is to add a step to your projects deployment processes with the following bash script to remove the BOM

sed -i '1 s/^\xef\xbb\xbf//' /path/to/deployment/*.conf

[paddie]

@DamianMac the link you provided doesn't give us any insight into why this was closed. We are running into this issue now, quite a few years later though...

[DamianMac]

Sorry @paddie maybe report it to support @ octopus (I don't work there anymore).
But if three people hit it in 3 and a half years it might not be the highest priority :)

[paddie]

Ha, I will @DamianMac :)

Yeah, we're also not sure exactly why it started happening now and the one team that's been hit by it (out of 15 other ones with around 300 projects), and we're also just performing a workaround so we don't have to wait for a fix.

Have a good day!

[droyad]

@paddie Does #4613 sound like the problem? If not, contact support with the details, including sample files and your configuration.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.