This repo builds and publishes the Terraform vsphere provider bindings for CDK for Terraform.
The npm package is available at https://www.npmjs.com/package/@cdktf/provider-vsphere.
npm install @cdktf/provider-vsphere
The PyPI package is available at https://pypi.org/project/cdktf-cdktf-provider-vsphere.
pipenv install cdktf-cdktf-provider-vsphere
The Nuget package is available at https://www.nuget.org/packages/HashiCorp.Cdktf.Providers.Vsphere.
dotnet add package HashiCorp.Cdktf.Providers.Vsphere
The Maven package is available at https://mvnrepository.com/artifact/com.hashicorp/cdktf-provider-vsphere.
<dependency>
<groupId>com.hashicorp</groupId>
<artifactId>cdktf-provider-vsphere</artifactId>
<version>[REPLACE WITH DESIRED VERSION]</version>
</dependency>
The go package is generated into the github.com/cdktf/cdktf-provider-vsphere-go package.
go get github.com/cdktf/cdktf-provider-vsphere-go/vsphere/<version>
Where <version> is the version of the prebuilt provider you would like to use e.g. v11. The full module name can be found
within the go.mod file.
Find auto-generated docs for this provider here:
You can also visit a hosted version of the documentation on constructs.dev.
This project is explicitly not tracking the Terraform vsphere provider version 1:1. In fact, it always tracks latest of ~> 2.2 with every release. If there are scenarios where you explicitly have to pin your provider version, you can do so by generating the provider constructs manually.
These are the upstream dependencies:
If there are breaking changes (backward incompatible) in any of the above, the major version of this project will be bumped.
Please report bugs and issues to the CDK for Terraform project:
This is mostly based on Projen, which takes care of generating the entire repository.
There's a custom project builder which encapsulate the common settings for all cdktf prebuilt providers.
The provider version can be adjusted in ./.projenrc.js.
The repository is managed by CDKTF Repository Manager.
