backup-agent logs errors about invalid character (\n) in the Azure storage URL. The secret does not contain the newline:
and even if we put newline into it, the error is the same (with only one \n in it, not two).
I also manually decoded a b64 value of the secret to be 100% sure that it doesn’t contain a newline.
I don’t expect that this is a bug with 100% repro, because the impact would be too big, but maybe anybody encountered such problem? Or maybe you have any idea how to debug it?
Setup backups with azure blob storage and provide AZURE_STORAGE_ACCOUNT_KEY and AZURE_STORAGE_ACCOUNT_NAME in secret.
every 5 seconds:
│ 2023-10-26T10:28:40.000+0000 E [agentCheckup] check storage connection: unable to get storage: parse “https://fakestoragename\n.blob.core.windows.net/fakecontainer”: net/url: invalid control character in URL │
Expected working backups
Error connecting to blob and no backups performed