mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
14 lines
1.2 KiB
Plaintext
14 lines
1.2 KiB
Plaintext
---
|
||
title: "Pulumi"
|
||
description: "Using KMS with Pulumi via the Terraform Bridge"
|
||
---
|
||
|
||
KMS can be integrated with Pulumi by leveraging Pulumi’s [Terraform Bridge](https://www.pulumi.com/blog/any-terraform-provider/),
|
||
which allows Terraform providers to be used seamlessly within Pulumi projects. This enables infrastructure and platform teams to manage KMS secrets and resources
|
||
using Pulumi’s familiar programming languages (including TypeScript, Python, Go, and C#), without any change to existing workflows.
|
||
|
||
The Terraform Bridge wraps the [KMS Terraform provider](https://registry.terraform.io/providers/KMS/kms/latest/docs) and exposes its resources (such as `kms_secret`, `kms_project`, and `kms_service_token`)
|
||
in a Pulumi-compatible interface. This makes it easy to integrate secret management directly into Pulumi-based IaC pipelines, ensuring secrets stay in sync with
|
||
the rest of your cloud infrastructure. Authentication is handled through the same methods as Terraform: using environment variables such as `KMS_TOKEN` and `KMS_SITE_URL`.
|
||
|
||
By bridging the KMS provider, teams using Pulumi can adopt secure, centralized secrets management without compromising on their toolchain or language preferences. |