A Terraform Provider which adds support for Proxmox solutions.
- Terraform 0.13+
- Go 1.15+ (to build the provider plugin)
- GoReleaser 0.155+ (to build the provider plugin)
-
Clone the repository to
$GOPATH/src/github.com/danitso/terraform-provider-proxmox
:$ mkdir -p "${GOPATH}/src/github.com/danitso" $ cd "${GOPATH}/src/github.com/danitso" $ git clone [email protected]:danitso/terraform-provider-proxmox
-
Enter the provider directory and build it:
$ cd "${GOPATH}/src/github.com/danitso/terraform-provider-proxmox" $ make build
You can find the latest release and its documentation in the Terraform Registry.
In order to test the provider, you can simply run make test
.
$ make test
Tests are limited to regression tests, ensuring backwards compability.
Due to limitations in the Proxmox VE API, certain actions need to be performed using SSH. This requires the use of a PAM account (standard Linux account).
Proxmox VE is not currently supporting VMware disk images directly. However, you can still use them as disk images by using this workaround:
resource "proxmox_virtual_environment_file" "vmdk_disk_image" {
content_type = "iso"
datastore_id = "datastore-id"
node_name = "node-name"
source_file {
# We must override the file extension to bypass the validation code in the Proxmox VE API.
file_name = "vmdk-file-name.img"
path = "path-to-vmdk-file"
}
}
resource "proxmox_virtual_environment_vm" "example" {
...
disk {
datastore_id = "datastore-id"
# We must tell the provider that the file format is vmdk instead of qcow2.
file_format = "vmdk"
file_id = "${proxmox_virtual_environment_file.vmdk_disk_image.id}"
}
...
}
Due to limitations in the Proxmox VE API, certain files need to be uploaded using SFTP. This requires the use of a PAM account (standard Linux account).