Maksym

Ok, I tried to use env vars, but now I got another error: ``` frpa1-cg8332k1s:xenorchestra mkursin$ terraform plan Refreshing Terraform state in-memory prior to plan... The refreshed state will be...

Ah... I understood what you meant when you said about ws/wss. ws is used for http and wss for https. Ok, so I'm waiting for a fix. Thanks

I performed a quick source code modification - switched ws to wss and now connection successful. But... I got another error: ``` 1 error(s) occurred: * xenorchestra_vm.bar: 1 error(s) occurred:...

BTW - using cloud_config as a sticky required option is not a good idea cuz terraform has builtin provisioning feature.

> But... I got another error: Bellow you can find xenorchestra_vm resouce config: ``` resource "xenorchestra_vm" "bar" { memory_max = 1073733632 cpus = 1 cloud_config = "${xenorchestra_cloud_config.bar.template}" name_label = "idmbs-testvm2-disk1"...

@ddelnano thanks for fixes As for latest error: I checked logs and found following error: `2019-04-05T09:03:05.999Z - xo:api - [WARN] m0ps | vm.create(...) [6s] =!> Error: no object with UUID...

idmbs-hv002 added into the pool that contains only one host. But you are right. I suppose that terraform should "tell" XO on which pool/host VM should be deployed cuz during...

xo-cli output for **fb489777-f615-1207-119a-3ac5b94d2ff0** datastore: ``` { "type": "SR", "content_type": "user", "physical_usage": 248793915392, "name_description": "", "name_label": "idmbs-hv002-hdd01", "size": 1771339907072, "shared": false, "SR_type": "ext", "tags": [], "usage": 3135326126080, "VDIs": [ "b476f7e2-c0b5-4304-a372-3031d0d6e303",...

Yes, affinityHost is used for selecting exactly host in a pool on which VM will be placed. As for the pool selection method, probably @olivierlambert can clarify.

This feature will be extremely useful when there is a terragrunt monorepo with mocks. That's the only thing that is currently missing to implement a "run-all apply" style workflow.