Missing means of adding cloud_network_config resource to XO

[OTonGitHub]

According to the documentation here https://registry.terraform.io/providers/vatesfr/xenorchestra/latest/docs/resources/cloud_config there is a cloud_config resource. Which, obviously, adds a cloud config resource to XO. And you can see it from the UI or just list it via API maybe. You can also see it being written in the trace logs during terraform apply

This works as intended. but, XO also has a network config section, at least when I check from the UI. And this works correctly and as intended. But I don't see a resource to add any network configurations here from the Terraform provider.

However, it is definitely still usable, because, you can still create cloud config resources, and I think the cloud_config and cloud_network_config properties of the VM just simply expects are properly templated and syntactically correct file that cloud-init accepts.

So right now when building VMs, (as shown in the screenshot below) I can just create cloud configs, name them accordingly and point the VM to the correct files and cloud-init will work. Simple example below.

On the VM created, I can verify both files were OK for cloud-init with no issues as show below

But as you can see, from the XO UI, both files are placed in the cloud config area, as expected.
note that the files are named "kraken-cc" and kraken-net-cc" respectively, its not shown in the code as it was passed as a variable.

And also note that, this is just a test host, so don't worry in case I may seemed to have shared something sensitive, this is not prod or anything.

I suppose this is kind of a non issue, maybe I am misunderstanding or not reading the docs correctly here, please correct me if so. Anyway, I feel like, should be able to create resources for both cloud config and network config separately since XO supports that.

[gCyrille]

Hi @OTonGitHub
You actually create 2 xenorchestra_cloud_config resources (one for the cloud init config and the second for the network config), but you only use the template of each in the VM.

There is not "network config" resource in the provider, that's why it's not in the XO UI.

In fact, you can use the template directly without creating a "cloud_config" resource:

resource "xenorchestra_vm" "vm" {
  // ...
  // Using the xenorchestra_cloud_config template
  cloud_config         = xenorchestra_cloud_config.demo.template
  // Using the template without creating dedicated resource 
  cloud_network_config = <<EOF
#cloud-config
network:
  version: 2
  ethernets:
    enX0:
      dhcp4: true
      # addresses:
      #   - 10.1.135.3/16
      # gateway4: 10.1.0.1/16
      # nameservers:
      #   addresses:
      #     - 9.9.9.9
EOF
  // ...
}

[gCyrille]

I change the type to feature for future enhancement :)