Terraform CDK hcs Provider ~> 0.5
This repo builds and publishes the Terraform hcs Provider bindings for CDK for Terraform.
Available Packages
NPM
The npm package is available at https://www.npmjs.com/package/@cdktf/provider-hcs.
npm install @cdktf/provider-hcs
PyPI
The PyPI package is available at https://pypi.org/project/cdktf-cdktf-provider-hcs.
pipenv install cdktf-cdktf-provider-hcs
Nuget
The Nuget package is available at https://www.nuget.org/packages/HashiCorp.Cdktf.Providers.Hcs.
dotnet add package HashiCorp.Cdktf.Providers.Hcs
Maven
The Maven package is available at https://mvnrepository.com/artifact/com.hashicorp/cdktf-provider-hcs.
<dependency>
<groupId>com.hashicorp</groupId>
<artifactId>cdktf-provider-hcs</artifactId>
<version>[REPLACE WITH DESIRED VERSION]</version>
</dependency>
Go
The go package is generated into the github.com/cdktf/cdktf-provider-hcs-go package.
go get github.com/cdktf/cdktf-provider-hcs-go/hcs
Docs
Find auto-generated docs for this provider here: ./API.md You can also visit a hosted version of the documentation on constructs.dev.
Versioning
This project is explicitly not tracking the Terraform hcs Provider version 1:1. In fact, it always tracks latest of ~> 0.5 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.
Features / Issues / Bugs
Please report bugs and issues to the terraform cdk project:
Contributing
projen
This is mostly based on projen, which takes care of generating the entire repository.
cdktf-provider-project based on projen
There's a custom project builder which encapsulate the common settings for all cdktf providers.
Provider Version
The provider version can be adjusted in ./.projenrc.js.
Repository Management
The repository is managed by Repository Manager
1 maintainer
Metadata
1 maintainer
Release files for cdktf-cdktf-provider-hcs 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cdktf-cdktf-provider-hcs-2.0.0.tar.gz | 160.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cdktf_cdktf_provider_hcs-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 333.9 kB
Release files / cdktf-cdktf-provider-hcs-2.0.0.tar.gz
| Download URL | cdktf-cdktf-provider-hcs-2.0.0.tar.gz |
|---|---|
| Size | 160.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
994c4cdf95e31caa9eb1a756e2fb43119ea80478c44d5b9ceb97e906cc5d2731
|
|
BLAKE2b-256 checksum How to use checksums |
ffbf2eea8d32ed19351959e3092fa87ce0b33e0461c3f5cba7441a3fbb53126b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.0
|
Release files / cdktf_cdktf_provider_hcs-2.0.0-py3-none-any.whl
| Download URL | cdktf_cdktf_provider_hcs-2.0.0-py3-none-any.whl |
|---|---|
| Size | 173.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9053cabe998ad3110f9c5dc153b77663aaf22c276b67ee08032bf5e50afdab60
|
|
BLAKE2b-256 checksum How to use checksums |
06fabcdf95970f363e3f53a566e5695c7e3229f0c3fcca901d8c9937a7095391
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.0
|
Security for cdktf-cdktf-provider-hcs 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
