CODEWITHSUNDEEP
terraformterraform-provider-azurecloud-init
proximator
proximator

Reputation: 688

Terraform default script path

I am creating multiple VMs in Azure using cloud-init, they are created in parallel and when any of them fails, I can see in the logs:

Error: error executing "/tmp/terraform_876543210.sh": Process exited with status 1

But I have no way to figure out which VM is failing, I need to ssh each of them and check The script path seems to be defined for provisioning Terraform

Is there a way to override it also for cloud-init to something like: /tmp/terraform_vmName_876543210.sh ?

I am not using provisioner but cloud-init, any idea how I can force terraform to override the terraform sh file?

Below my script:

resource "azurerm_linux_virtual_machine" "example" {
  name                = "example-machine"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_resource_group.example.location
  size                = "Standard_F2"
  admin_username      = "adminuser"
  network_interface_ids = [
    azurerm_network_interface.example.id,
  ]

  admin_ssh_key {
    username   = "adminuser"
    public_key = file("~/.ssh/id_rsa.pub")
  }

  os_disk {
    caching              = "ReadWrite"
    storage_account_type = "Standard_LRS"
  }

  source_image_reference {
    publisher = "Canonical"
    offer     = "UbuntuServer"
    sku       = "16.04-LTS"
    version   = "latest"
  }
  
    custom_data = base64encode(templatefile(
    "my-cloud-init.tmpl", {
      var1 = "value1"
      var2 = "value2"
    })
  )
}

And my cloud-init script:

## template: jinja
#cloud-config

runcmd:
- sudo /tmp/bootstrap.sh

write_files:

- path: /tmp/bootstrap.sh
  permissions: 00700
  content: |
    #!/bin/sh -e
    echo hello

Upvotes: 0

Views: 730

Answers (1)

Charles Xu
Charles Xu

Reputation: 31414

From the code you found for the Terraform, it shows:

DefaultUnixScriptPath is used as the path to copy the file to for remote execution on Unix if not provided otherwise.

It's the configuration for the remote execution. And for the remote execution of the SSH, you can set the source and the destination for the copy file in the provisioner "file".

But it's used to set the path in the remote VM, not the local machine that you execute the Terraform. And you can overwrite the file name like this:

provisioner "file" {
  source      = "conf/myapp.conf"
  destination = "/etc/terraform_$(var.vmName).conf"

  ...
}

Upvotes: 1

Related Questions