Synthetic test fails with INVALID_CHAR_IN_HEADER if entry in request_headers comes from data.local_file about terraform-provider-datadog

[HantingZhang2]

Hi @mariodescanva
the headerx-hub-signature-256 = data.local_file.sha256[each.key].content seem to be the cause of the INVALID_CHAR_IN_HEADER error, do you have the content of this header that might be an invalid character ?

[mariodescanva]

Hi @mariodescanva the headerx-hub-signature-256 = data.local_file.sha256[each.key].content seem to be the cause of the INVALID_CHAR_IN_HEADER error, do you have the content of this header that might be an invalid character ?

@HantingZhang2 I looked closer into the value that comes from datadog backend and turns out datadog doesn't prevent the provider from storing a new line in that field. It was hard to debug because in the UI, there is no way to tell whether it's a new line or not, unless you open up the browser console and try to edit the html tag.

That being said, should the provider validation be extended to not allow new line characters?