Product Overviews

Using OneFuse with Terraform

Issue link: https://resources.cloudbolt.io/i/1407488

Contents of this Issue

Navigation

Page 44 of 45

T E C H N I C A L G U I D E 44 disk { label = "disk0" size = data.vsphere_virtual_machine.template.disks.0.size eagerly_scrub = data.vsphere_virtual_machine.template.disks.0.eagerly_scrub thin_provisioned = data.vsphere_virtual_machine.template.disks.0.thin_provisioned } clone { template_uuid = data.vsphere_virtual_machine.template.id customize { linux_options { host_name = module.onefuse.hostname domain = module.onefuse.dns_suffix } network_interface { ipv4_address = module.onefuse.ip_address ipv4_netmask = 24 } ipv4_gateway = module.onefuse.gateway } } } If you look through the configuration you will see references to module.onfuse.hostname, module.onfuse.ip_address, module.onfuse.gateway, and module.onfuse.network. These are all passed in to the appropriate inputs to be used during the vSphere VM deployment.

Articles in this issue

Links on this page

view archives of Product Overviews - Using OneFuse with Terraform