Version 2.0.0 of our Pulumi provider is out! It leverages the Xen Orchestra API to manage your XCP-ng infrastructure as code.
💡
Why use the Xen Orchestra API instead of talking to each XCP-ng host directly?
Because XO already abstracts and centralizes everything. You don’t need to worry about which host runs what : the API gives you a unified, consistent way to manage your whole platform (VMs, storage, networks, and more). It's the smart layer on top of your infrastructure!
Because XO already abstracts and centralizes everything. You don’t need to worry about which host runs what : the API gives you a unified, consistent way to manage your whole platform (VMs, storage, networks, and more). It's the smart layer on top of your infrastructure!
This release aims to ensure that the provider is up to date with the latest version of the pulumi-terraform-bridge. This will make it easier to follow new Pulumi versions.
The underlying Terraform provider XenOrchestra is updated to version 0.31.1, which fixes:
- Issues with blocked operations when creating VMs. #344
- A problem where the
destroy_cloud_config_vdi_after_bootsetting was ignored when the VM wasn't running. #345
As the major version number suggests, this release introduces changes that break compatibility with previous versions (mostly deprecated functions and resources that have been removed).
Find the release in the Pulumi registry:
Xen Orchestra
Provides an overview of the Xen Orchestra Provider for Pulumi.
pulumi
Full Release Note:
Release v2.0.0 · vatesfr/pulumi-xenorchestra
This release aims to ensure that the provider is up to date with the latest version of the pulumi-terraform-bridge. This will make it easier to follow new Pulumi versions. What’s Changed Update RE…
GitHubvatesfr
from Xen Orchestra https://ift.tt/pADL72G
via IFTTT
No comments:
Post a Comment