mirrors/terraform-provider-proxmox
0
0
Fork 0
mirror of https://github.com/bpg/terraform-provider-proxmox.git synced 2025-06-30 02:31:10 +00:00
Code
e3dd31f55e
terraform-provider-proxmox/docs/data-sources/virtual_environment_vm2.md
Pavel Boldyrev e3dd31f55e
chore(vm2): add datasource implementation (#1318) 
* chore(vm2): add datasource implementation

---------

Signed-off-by: Pavel Boldyrev <627562+bpg@users.noreply.github.com>
2024-05-22 02:06:41 +00:00

2.2 KiB
Raw Blame History

layout title parent subcategory description
page proxmox_virtual_environment_vm2 Data Sources Virtual Environment This is an experimental implementation of a Proxmox VM datasource using Plugin Framework.

Data Source: proxmox_virtual_environment_vm2

!> DO NOT USE This is an experimental implementation of a Proxmox VM datasource using Plugin Framework.

Schema

Required

  • id (Number) The unique identifier of the VM in the Proxmox cluster.
  • node_name (String) The name of the node where the VM is provisioned.

Optional

  • clone (Attributes) The cloning configuration. (see below for nested schema)
  • cpu (Attributes) The CPU configuration. (see below for nested schema)
  • description (String) The description of the VM.
  • name (String) The name of the VM.
  • tags (Set of String) The tags assigned to the VM.
  • template (Boolean) Whether the VM is a template.
  • timeouts (Attributes) (see below for nested schema)

Nested Schema for clone

Required:

  • id (Number) The ID of the VM to clone.

Optional:

  • retries (Number) The number of retries to perform when cloning the VM (default: 3).

Nested Schema for cpu

Optional:

  • affinity (String) List of host cores used to execute guest processes, for example: '0,5,8-11'
  • architecture (String) The CPU architecture.
  • cores (Number) The number of CPU cores per socket.
  • flags (Set of String) Set of additional CPU flags.
  • hotplugged (Number) The number of hotplugged vCPUs.
  • limit (Number) Limit of CPU usage.
  • numa (Boolean) Enable NUMA.
  • sockets (Number) The number of CPU sockets.
  • type (String) Emulated CPU type.
  • units (Number) CPU weight for a VM

Nested Schema for timeouts

Optional:

  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.