This repo builds and publishes the Terraform digitalocean Provider bindings for cdktf.

The npm package is available at https://www.npmjs.com/package/@cdktf/provider-digitalocean.

npm install @cdktf/provider-digitalocean

The PyPI package is available at https://pypi.org/project/cdktf-cdktf-provider-digitalocean.

pipenv install cdktf-cdktf-provider-digitalocean

The Nuget package is available at https://www.nuget.org/packages/HashiCorp.Cdktf.Providers.Digitalocean.

dotnet add package HashiCorp.Cdktf.Providers.Digitalocean

The Maven package is available at https://mvnrepository.com/artifact/com.hashicorp/cdktf-provider-digitalocean.

<dependency>
    <groupId>com.hashicorp</groupId>
    <artifactId>cdktf-provider-digitalocean</artifactId>
    <version>[REPLACE WITH DESIRED VERSION]</version>
</dependency>

Find auto-generated docs for this provider here: ./API.md

This project is explicitly not tracking the Terraform digitalocean Provider version 1:1. In fact, it always tracks latest of ~> 2.19 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:

• Terraform CDK
• Terraform digitalocean Provider
• Terraform Engine

If there are breaking changes (backward incompatible) in any of the above, the major version of this project will be bumped. While the Terraform Engine and the Terraform digitalocean Provider are relatively stable, the Terraform CDK is in an early stage. Therefore, it's likely that there will be breaking changes.

Please report bugs and issues to the terraform cdk project:

• Create bug report
• Create feature request

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

The provider version can be adjusted in ./.projenrc.js.

The repository is managed by Repository Manager