Offline
The provider is now available on the Pulumi official Registry 
https://www.pulumi.com/registry/packages/xenorchestra/
We added example for Yaml in the documentation.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2
Hello,
If you want to discuss the Pulumi Provider in detail, let discuss here: https://xcp-ng.org/forum/topic/10592/pulumi-xen-orchestra-news
@nathanael-h said in DevOps Megathread: what you need and how we can help!:
Hello there, we released a new Pulumi Xen Orchestra provider last month ! It's worth noting that the work on this was started by some contributors from DESY, and that now we (Vates) commit to support and maintain it. This demonstrate the strength of joined work from both community and Vates on free and open source softwares
So what is offered is to declare your infrastructure as code, in Javascript or Typescript, Go, or Python (pick the one you prefer
) and to deploy, maintain, and update it.
The Pulumi Xen Orchestra provider is now available with Dotnet SDK!
@vates/pulumi-xenorchestrapulumi-xenorchestragithub.com/vatesfr/pulumi-xenorchestra/sdkPulumi.XenorchestraThe Pulumi schema doesn't support u64 (or i64), so we convert to a float64, which should get us at least 2^52 bits of precision while minimizing the breaking change (int -> float) for our users.
🟡 inputs: "memoryMax" type changed from "integer" to "number"🟡 properties: "memoryMax" type changed from "integer" to "number"🟡 "xenorchestra:index/VmDisk:VmDisk": properties: "size" type changed from "integer" to "number"Replace pulumi.Int(...) with pulumi.Float64(...)
Other SDKs do not seem to be affected by the changes.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.0
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2
Upgrade the Pulumi SDK and others libraries to the latest version and provider Java sdk.
If you are using Pulumi Xen Orchestra, please share your experiences and needs with us 
@wezke you are welcome. let us know if you find the explanation for the problem with the template
The provider is now available on the Pulumi official Registry
https://www.pulumi.com/registry/packages/xenorchestra/
We added example for Yaml in the documentation.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2
Hello,
If you want to discuss the Pulumi Provider in detail, let discuss here: https://xcp-ng.org/forum/topic/10592/pulumi-xen-orchestra-news
@nathanael-h said in DevOps Megathread: what you need and how we can help!:
Hello there, we released a new Pulumi Xen Orchestra provider last month ! It's worth noting that the work on this was started by some contributors from DESY, and that now we (Vates) commit to support and maintain it. This demonstrate the strength of joined work from both community and Vates on free and open source softwares
So what is offered is to declare your infrastructure as code, in Javascript or Typescript, Go, or Python (pick the one you prefer
The Pulumi Xen Orchestra provider is now available with Dotnet SDK!
@vates/pulumi-xenorchestrapulumi-xenorchestragithub.com/vatesfr/pulumi-xenorchestra/sdkPulumi.XenorchestraThe Pulumi schema doesn't support u64 (or i64), so we convert to a float64, which should get us at least 2^52 bits of precision while minimizing the breaking change (int -> float) for our users.
🟡 inputs: "memoryMax" type changed from "integer" to "number"🟡 properties: "memoryMax" type changed from "integer" to "number"🟡 "xenorchestra:index/VmDisk:VmDisk": properties: "size" type changed from "integer" to "number"Replace pulumi.Int(...) with pulumi.Float64(...)
Other SDKs do not seem to be affected by the changes.
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.0
Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2
Upgrade the Pulumi SDK and others libraries to the latest version and provider Java sdk.
If you are using Pulumi Xen Orchestra, please share your experiences and needs with us
@wezke you are welcome. let us know if you find the explanation for the problem with the template
@wezke Hi, I have no problem running your terraform plan, maybe there is a problem with the template you are using? How did you create it?
There is no warning during the tf execution?