Bug: Buildmaster 6.2.14 (Build 17) Configuration Template Values containing equals character

[antony.booth_1029]

Entering a value containing an equals sign '=' will trim all remaining characters, including the equals character.

So: -

abcdefghijklmnopqrstuvwxyz1234567890=== becomes abcdefghijklmnopqrstuvwxyz1234567890 (All the equals trimmed)
abcdefghijklmnopqrstuvwxyz=1234567890 becomes abcdefghijklmnopqrstuvwxyz (all the numbers and equals trimmed)

This is problematic if you want to store something like a base64 encoded string that terminates with 2 equals. E.g: -

abcdefghijklmnopqrstuvwxyz1234567890== becomes abcdefghijklmnopqrstuvwxyz1234567890

The workaround for base 64 is to omit the '==' and keep it in the template. I.E: -

<something key="MyKey" value="${variable}==" />

However, this wouldn't work for something ,like a connection string: -

<connection name="theServer" connectionString="ServerName=${server}; user=${username}; password=${somePasswordThatMightHaveAnEqualsInIt};" />

[rhessinger]

Hi @antony-booth_1029 ,

It looks like this is just an issue with the editor. If you set the value to include the = sign and save it. When you run everything is fine and the value includes the = sign. When you open to edit it though, the = is stripped off, and then when you save it, it removes = from the config file. I am currently working to correct the issue.

Thanks,
Rich

[rhessinger]

Hi @antony-booth_1029 ,

I have fixed this issue and it will be released in BuildMaster 6.2.15 which is due out on July 17. I'll post back here if anything changes.

Thanks,
Rich