template files created on a Windows client will follow the CLRF line ending convention. this becomes problematic when the agent start-up script is executed on a Linux-based workspace (which expects the LF line ending convention), resulting in the following errors:

/bin/bash: line 1: $'\r': command not foundzsh:2: command not found: ^M

@mafredri suggested we could auto-process terraform files from CRLF to LF upon import. from theterraform docs:

Terraform accepts configuration files with either Unix-style line endings (LF only) or Windows-style line endings (CR then LF), but the idiomatic style is to use the Unix convention, and so automatic configuration formatting tools may automatically transform CRLF endings to LF.