This release is a pre-release and may not be stable for production use.
Unleash Pulumi Provider
A Pulumi provider for Unleash, bridged from
the official Unleash/terraform-provider-unleash
using the Pulumi Terraform Bridge.
Because it bridges the upstream Terraform provider directly, resources and data sources come from the same schema rather than a parallel reimplementation, so the two stay in lockstep as the upstream provider evolves.
Status: not published
Nothing has been released to npm, PyPI, NuGet, or the Pulumi Registry, and the package names are provisional. This repository exists so the provider can be evaluated before it has a permanent home — the intent is to contribute it to Pulumiverse, the Pulumi community organization. Naming and publishing are deliberately deferred until that conversation concludes, so there is exactly one package identity and no orphaned early releases.
To use it today, build from source.
Building from source
Prerequisites: Go 1.25+, pulumictl,
mise, the Pulumi CLI, Node.js, Yarn, Python 3, and the .NET SDK.
pulumi plugin install converter terraform # required - schema generation uses pulumiConvert
make tfgen # generate the Pulumi schema from the upstream Terraform provider
make provider # build bin/pulumi-resource-unleash
make build_sdks # generate and build the dotnet, go, nodejs and python SDKs
Configuration
| Option | Environment variable | Notes |
|---|---|---|
baseUrl |
UNLEASH_URL |
Everything before /api |
authorization |
UNLEASH_AUTH_TOKEN |
Admin API token; marked secret |
maxConcurrentRequests |
UNLEASH_MAX_CONCURRENT_REQUESTS |
Upstream default is 2 |
The upstream Terraform provider also accepts a bare AUTH_TOKEN as a fallback. This provider
deliberately does not, because an unscoped AUTH_TOKEN sitting in a shell or CI environment would
silently authenticate against Unleash. Use UNLEASH_AUTH_TOKEN.
Resource coverage and the Enterprise gap
All 13 resources and 8 data sources from the upstream provider are bridged and present in the generated schema.
Automated end-to-end tests cover only what an open-source Unleash server can actually do. Unleash
OSS ships a fixed default project plus development/production environments, and its community
build registers no write routes for most administrative APIs — creating projects, environments,
users, groups, roles or service accounts, and configuring OIDC/SAML all require an Enterprise
licence. The upstream provider's own acceptance tests set UNLEASH_LICENSE for this reason.
| Resource | Live test coverage |
|---|---|
ApiToken |
Real create/destroy against OSS Unleash in CI |
| Everything else | Compile and schema generation only |
The ApiToken test (examples/oss-ts, driven by TestOssTs in
examples/examples_nodejs_test.go) starts its own Unleash + Postgres containers via
testcontainers-go, so it runs identically locally
and in CI with no setup step. The root docker-compose.yml is still there
as a convenience for running the example by hand (docker compose up + pulumi up) — it is
optional and the test does not depend on it.
Contributions widening this are welcome, but note that a licence secret is not available to pull requests from forks, so fork CI cannot exercise Enterprise resources either.
Versioning
The major version tracks the upstream Terraform provider's major version, matching the convention
other bridged community providers use. This provider's 3.x line bridges
terraform-provider-unleash 3.x.
A note on the upstream Go module path
github.com/Unleash/terraform-provider-unleash declares no /v3 module path suffix despite tagging
v3.x releases, so Go cannot resolve any of its v2 or v3 tags as a dependency — the module proxy's
@latest for that path resolves to v1.4.1. This provider therefore pins the upstream at a
pseudo-version rather than a release tag. Adding the suffix upstream would make this a normal semver
dependency.
License
Apache-2.0 — see LICENSE.
Metadata
Release files for pulumiverse-unleash 3.0.0a1786027366
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 | Actions |
|---|---|---|---|---|
| pulumiverse_unleash-3.0.0a1786027366.tar.gz | 32.5 kB | Without provenance | Details for pulumiverse_unleash-3.0.0a1786027366.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pulumiverse_unleash-3.0.0a1786027366-py3-none-any.whl | Python 3 | none | any | Details for pulumiverse_unleash-3.0.0a1786027366-py3-none-any.whl |
Total release size: 90.5 kB
Release files / pulumiverse_unleash-3.0.0a1786027366.tar.gz
| Download URL | pulumiverse_unleash-3.0.0a1786027366.tar.gz |
|---|---|
| Size | 32.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fc9811f757a81f70bff6832558edad0e49fd6698b15d115240b2fefe538dcd3
|
|
BLAKE2b-256 checksum How to use checksums |
900586119d4fe3373c6cf446a0dfe3c6b273a17b9aec0ad8a0597ef8715c1e22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.8
|
Release files / pulumiverse_unleash-3.0.0a1786027366-py3-none-any.whl
| Download URL | pulumiverse_unleash-3.0.0a1786027366-py3-none-any.whl |
|---|---|
| Size | 58.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
59a802422243760b6c5dd247cd075c6a57af56df10835e8d2fbd2c649cb02bb4
|
|
BLAKE2b-256 checksum How to use checksums |
716bb190c2c0d4324e397666283a678f4102d179985a4d3277073b2ea8dfe07d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.8
|
Security for pulumiverse-unleash 3.0.0a1786027366
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.