Skip to main content

CDKTN prebuilt bindings for vancluever/acme provider version 3.2.2

This repo builds and publishes the Terraform acme provider bindings for CDK Terrain.

Available Packages

NPM

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

npm install @cdktn/provider-acme

PyPI

The PyPI package is available at https://pypi.org/project/cdktn-provider-acme.

pipenv install cdktn-provider-acme

Nuget

The Nuget package is available at https://www.nuget.org/packages/Io.Cdktn.Providers.Acme.

dotnet add package Io.Cdktn.Providers.Acme

Maven

The Maven package is available at https://mvnrepository.com/artifact/io.cdktn/cdktn-provider-acme.

<dependency>
    <groupId>io.cdktn</groupId>
    <artifactId>cdktn-provider-acme</artifactId>
    <version>[REPLACE WITH DESIRED VERSION]</version>
</dependency>

Go

The go package is generated into the github.com/cdktn-io/cdktn-provider-acme-go package.

go get github.com/cdktn-io/cdktn-provider-acme-go/acme/<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.

Docs

Find auto-generated docs for this provider here:

You can also visit a hosted version of the documentation on constructs.dev.

Versioning

This project is explicitly not tracking the Terraform acme provider version 1:1. In fact, it always tracks latest of ~> 3.0 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 CDK Terrain project:

Contributing

Projen

This is mostly based on Projen, which takes care of generating the entire repository.

cdktn-provider-project based on Projen

There's a custom project builder which encapsulate the common settings for all cdktn prebuilt providers.

Provider Version

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

Repository Management

The repository is managed by CDKTN Repository Manager.

Metadata

Release files for cdktn-provider-acme 17.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cdktn-provider-acme 17.0.1
File Size Uploaded Provenance Actions
cdktn_provider_acme-17.0.1.tar.gz 108.8 kB With provenance Details for cdktn_provider_acme-17.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cdktn-provider-acme 17.0.1
File Interpreter ABI Platform Actions
cdktn_provider_acme-17.0.1-py3-none-any.whl Python 3 none any Details for cdktn_provider_acme-17.0.1-py3-none-any.whl

Total release size: 218.9 kB

Release files / cdktn_provider_acme-17.0.1.tar.gz

Download URL cdktn_provider_acme-17.0.1.tar.gz
Size 108.8 kB
Tags Source
SHA-256 checksum
How to use checksums
e6c0a6bd8bedf2a35ff81aee60024de72bd86752ee32d9d858fc8f09416b12be
BLAKE2b-256 checksum
How to use checksums
7139516f69ba23e89480a0c2b2b0cc59224f87644c3b6d591a1e02a3860f1b07
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.15.1

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Release files / cdktn_provider_acme-17.0.1-py3-none-any.whl

Download URL cdktn_provider_acme-17.0.1-py3-none-any.whl
Size 110.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5d8c81afc8dad0c5cad1c3d2829bfafae3387d143844fbfd81a8b466bc2a764d
BLAKE2b-256 checksum
How to use checksums
e3f0e2147dae6aba81efa0a49d119df34cd8764491847d5f0f1b531988093a7a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.15.1

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Security for cdktn-provider-acme 17.0.1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cdktn_provider_acme-17.0.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page