Revision history [back]

Quite by chance I managed to figure out why this is failing. When creating the terraform "templatecloudinitconfig" I had not specified a filename for each of these scripts. According to the terraform documentation this is "optional" and I had assumed that a generic/temporary name would be created.

The eventual working configuration that worked is:

data "template_cloudinit_config" "config" {
  gzip          = true
  base64_encode = true

  part {
    filename     = "disable-ipv6.ps1"
    content_type = "text/x-shellscript"
    content      = file("${path.cwd}/scripts/disable-ipv6.ps1")
  }

  part {
    filename     = "configure-firewalls.ps1"
    content_type = "text/x-shellscript"
    content      = file("${path.cwd}/scripts/configure-firewalls.ps1")
  }
}

Should this be logged as a bug? If filename is considered optional shouldn't cloudbase init handle this when processing multipart mimedata?

Quite by chance I managed to figure out why this is failing. When creating the terraform "templatecloudinitconfig" template_cloudinit_config I had not specified a filename for each of these scripts. According to the terraform documentation this is "optional" and I had assumed that a generic/temporary name would be created.

The eventual working configuration that worked is:

data "template_cloudinit_config" "config" {
  gzip          = true
  base64_encode = true

  part {
    filename     = "disable-ipv6.ps1"
    content_type = "text/x-shellscript"
    content      = file("${path.cwd}/scripts/disable-ipv6.ps1")
  }

  part {
    filename     = "configure-firewalls.ps1"
    content_type = "text/x-shellscript"
    content      = file("${path.cwd}/scripts/configure-firewalls.ps1")
  }
}

Should this be logged as a bug? If filename is considered optional shouldn't cloudbase init handle this when processing multipart mimedata?