Losing whitespace/indentation in bootcmd scripts

[chancez]

I'm attempting to write a bootcmd that uses a bash heredoc to write some YAML to provide some config overrides to cloudinit before the network is initialized, but the problem is that lima strips whitespace when writing bootcmds to the bootcmd in the user-data:

lima/pkg/cidata/cidata.go

Lines 491 to 499 in e21b634

	if f.Mode == limatype.ProvisionModeBoot {
	lines := []string{}
	for _, line := range strings.Split(*f.Script, "\n") {
	if line == "" {
	continue
	}
	lines = append(lines, strings.TrimSpace(line))
	}
	bootCmds = append(bootCmds, BootCmds{Lines: lines})

Here's the relevant portion of my lima.yaml:

provision:
- mode: boot
  script: |
    cat <<EOF > /etc/cloud/cloud.cfg.d/99-lima1-disable-route.cfg
    ethernets:
      lima1:
        dhcp4-overrides:
          use-routes: false
    EOF

And here's what gets rendered in user-data:

bootcmd:
- |
  # We need to embed the params.env as a here-doc because /mnt/lima-cidata is not yet mounted
  while read -r line; do [ -n "$line" ] && export "$line"; done <<'EOF'
  EOF
  cat <<EOF > /etc/cloud/cloud.cfg.d/99-lima1-disable-route.cfg
  ethernets:
  lima1:
  dhcp4-overrides:
  use-routes: false
  EOF

[songponssw]

I think there is a mode: data for writing configuration during provision. Example

Instance config.yml

provision:
- mode: data
  path: /etc/cloud/cloud.cfg.d/99-lima1-disable-route.cfg
  owner: root:root
  permissions: '0755'
  content: |
      ethernets:
        lima1:
          dhcp4-overrides:
            use-routes: false

Result

cat /etc/cloud/cloud.cfg.d/99-lima1-disable-route.cfg
ethernets:
  lima1:
    dhcp4-overrides:
      use-routes: false

[jandubois]

that lima strips whitespace when writing bootcmds to the bootcmd in the user-data

That sounds like a bug to me.

I think there is a mode: data for writing configuration during provision.

There is, but this probably happens too late in the boot sequence to write network config files.

[jandubois]

@chancez I've opened #4381 to address this. If you have time, could you test it? Also please confirm that having blank lines in boot commands is not an issue either?