Keyvaultsecrets with umlauts are passed incorrectly and unmasked

[juliandittmann]

Steps to reproduce:

• Create a secret with umlauts (ö,ä,ü, ... )
• Run CI/CD workflow

Note: I used a keyvault.

The secrets are recieved correctly from the vault but somehow are passed incorrectly.
This results in unmasking secrets and futher errors.

Example:

[freddydk]

I have spent a lot of time trying to figure out a way to make this work - and I will have to give up.
I do see this as a bug in GitHub, which I assume they will fix at some point in time.
At the same time, it is crucial that secrets are not revealed by the system, so from the next version of AL-Go - you will get this error if a secret contains characters, which are outside the range of 32..126

One workaround would be to implement support for some secrets could be base64 encoded (like provide :::: as your secret value and I will decode when used). This would be quite a lot of work, and might not be needed. I will assess based on feedback.

[freddydk]

I will mark the bug as fixed, as it will no longer reveal your secrets, knowing that you will have to change your URL to NOT contain special characters.

[freddydk]

Released in preview

[freddydk]

Shipped in v1.5