These two bugs have been fixed in the latest release

Release v1.5.2

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.

https://github.com/vatesfr/pulumi-xenorchestra/

---

Release v1.5.0

The Pulumi Xen Orchestra provider is now available with Dotnet SDK!

• JavaScript/TypeScript: @vates/pulumi-xenorchestra
• Python: pulumi-xenorchestra
• Go: github.com/vatesfr/pulumi-xenorchestra/sdk
• .NET: Pulumi.Xenorchestra

What's Changed

• Feat: Add dotnet support
• Add docs for Dotnet SDK and unify examples

The 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.

List of properties to be updated from "integer" to "number"/float64:

Resources

• "xenorchestra:index/vm:Vm":
  • 🟡 inputs: "memoryMax" type changed from "integer" to "number"
  • 🟡 properties: "memoryMax" type changed from "integer" to "number"

Types

• 🟡 "xenorchestra:index/VmDisk:VmDisk": properties: "size" type changed from "integer" to "number"

How to migrate Golang stack code

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

---

Release v1.5.2

• The provider is now available on the Pulumi official Registry: https://www.pulumi.com/registry/packages/xenorchestra/
• Added example for Yaml

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2

---

What's next?

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