Manage balloon memory

[MOURADMAZOUZ]

Checklist

• [X] Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?

  • [X] Make sure you explain why this option is important to you, why it should be important to everyone. Describe your use-case with detail and provide examples where possible.
  • [ ] If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
  • [ ] Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation

• [ ] Is it a bug or something that does not work as expected? Please make sure you fill the version information below:

Description of Issue/Question

By default terraform module don't manage over allocate memory and allocate all memory on start up. Is it possible to add option "MemoryUse" to be able to do over allocate memory on deployment ?

Setup

I try to patch with success this code,:

terraform-provider-libvirt/libvirt$ diff resource_libvirt_domain.go 
70,75d69
<           "currentmemory": {
<               Type:     schema.TypeInt,
<               Optional: true,
<               Default:  256,
<               ForceNew: true,
<           },
518,521d511
<   domainDef.CurrentMemory = &libvirtxml.DomainCurrentMemory{
<       Value: uint(d.Get("currentmemory").(int)),
<       Unit:  "MiB",
<   }
840d829
<   d.Set("currentmemory", domainDef.CurrentMemory)

Default at 0 allocate all memory, it's like non over allocate memory

(Please provide the full main.tf file for reproducing the issue (Be sure to remove sensitive information)

[scabala]

Hi @MOURADMAZOUZ, this is very nice feature. I have trouble following patch you presented. AFAIU, it should be possible to specify CurrentMemory via additional argument, right? Would you be interested in providing a PR?