terraform-provider-ghpvaultsecret

A Terraform provider that manages the ghp token secrets engine (vault-plugin-secrets-ghp) on HashiCorp Vault or OpenBao, so the engine's mount, config, and roles can be driven declaratively (e.g. from terraform-vault).

Source address: git.unkin.net/unkin/ghpvaultsecret (declare it under the local name ghpvaultsecret, so its resources are ghpvaultsecret_*).

Resources

Resource	Manages
ghpvaultsecret_secret_backend	Mounts the engine at a path and writes its config (ghp base URL, TLS, seeded service token).
ghpvaultsecret_secret_role	A role: token_type, installation_id, app_record_id, repositories, scopes, session_prefix, ttl, max_ttl.

Usage

terraform {
  required_providers {
    ghpvaultsecret = {
      source = "git.unkin.net/unkin/ghpvaultsecret"
    }
  }
}

provider "ghpvaultsecret" {
  # address / token fall back to VAULT_ADDR / VAULT_TOKEN.
}

resource "ghpvaultsecret_secret_backend" "ghp" {
  path        = "ghp"
  base_url    = "https://ghp.unkin.net"
  admin_token = var.ghp_admin_token
}

resource "ghpvaultsecret_secret_role" "ci" {
  backend         = ghpvaultsecret_secret_backend.ghp.path
  name            = "ci"
  token_type      = "agent"
  installation_id = 12345
  repositories    = ["unkin/prodenv"]
  scopes          = ["contents:read", "pull_requests:write"]
  ttl             = 3600
  max_ttl         = 28800
}

Notes

• admin_token is write-only: Vault never returns it, so it is preserved in Terraform state and does not show drift. ca_cert is likewise write-only and preserved.
• Writing config makes the engine verify the service token against ghp (it must authenticate as a ghp admin), so a bad URL or token fails the apply.
• token_type defaults to agent; agent roles require installation_id. Proxy roles are OAuth-backed and ignore installation_id / app_record_id.
• repositories and scopes are optional; an empty set is open-scoped (all repositories / all permissions the installation allows). Scope entries are permission:level where level is read or write.

Import

terraform import ghpvaultsecret_secret_backend.ghp ghp
terraform import ghpvaultsecret_secret_role.ci ghp/roles/ci

Development

make build      # build the provider binary
make install    # install into ~/.terraform.d/plugins for local use
make test       # unit tests (race)
make e2e        # apply real terraform against Vault + a mock ghp (Docker)
make package    # build the release zip

Releases are tag-driven (make patch|minor|major): a Woodpecker pipeline builds terraform-provider-ghpvaultsecret_<version>_linux_amd64.zip and PUTs it to the artifactapi terraform registry (.../api/v2/remotes/terraform-unkin/files/unkin/ghpvaultsecret/<file>), which signs it server-side. Install it via the bare source address above.