This repo builds and publishes the Terraform opsgenie Provider bindings for CDK for Terraform.
The npm package is available at https://www.npmjs.com/package/@rhizo-co/provider-opsgenie.
npm install @rhizo-co/provider-opsgenie
The PyPI package is available at https://pypi.org/project/rhizo-co-cdktf-provider-opsgenie.
pipenv install rhizo-co-cdktf-provider-opsgenie
The Nuget package is available at https://www.nuget.org/packages/HashiCorp.Cdktf.Providers.Opsgenie.
dotnet add package HashiCorp.Cdktf.Providers.Opsgenie
The Maven package is available at https://mvnrepository.com/artifact/com.hashicorp/cdktf-provider-opsgenie.
<dependency>
<groupId>com.hashicorp</groupId>
<artifactId>cdktf-provider-opsgenie</artifactId>
<version>[REPLACE WITH DESIRED VERSION]</version>
</dependency>
The go package is generated into the github.com/rhizo-co/cdktf-provider-opsgenie-go package.
go get github.com/rhizo-co/cdktf-provider-opsgenie-go/opsgenie
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 opsgenie Provider version 1:1. In fact, it always tracks latest of ~> 0.6.33 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 opsgenie Provider
- This links to the minimum version being tracked, you can find the latest released version in our releases
- Terraform Engine
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 terraform cdk 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 providers.
The provider version can be adjusted in ./.projenrc.js.
The repository is managed by Repository Manager