Binary files in TM configs
briantopping opened this issue · comments
Brian Topping commented
When TM file
config is used with binary base64 data, the file is corrupted and the size of the file at stage input is larger than the original file encoded with the base64
utility.
I'm not a UTF-8 expert or read all the code paths, but I presume it's due to usage of string()
typecasting and possibly due to protobufs internal to Argo. It seems likely there is some code point expansion going on as a result.