unkinben
a960757ab2
Why: teabot's implementer and reviewer bot users should mint ephemeral, scoped Gitea tokens on demand instead of holding standing personal access tokens (Gitea tokens never expire on their own). This registers and mounts the new vault-plugin-secrets-gitea engine and declares its roles, mirroring the rancher engine wiring. Change: - Register the plugin in the catalog (config/plugins/vault-plugin-secrets-gitea.yaml) pinned to the released v0.1.0 binary sha256. - Add gitea_secret_backend + gitea_secret_backend_role modules and wire them through config.hcl, terragrunt.hcl, and vault_cluster variables/main, using the giteavaultsecret provider (terraform-unkin registry, v0.1.0). - Mount the engine at gitea/ against https://git.unkin.net; seeded site-admin credentials are read from KV (service/vault/au/syd1/secret_backend/gitea/config). - Add teabot-implementer (write:repository, write:issue) and teabot-reviewer (read:repository, write:issue) roles, ttl 1h / max_ttl 4h. Claude-Session: https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv
15 lines
562 B
YAML
15 lines
562 B
YAML
# Role minting ephemeral tokens for the teabot-implementer bot user.
|
|
# The implementer clones/pushes code and opens pull requests, so it gets write
|
|
# on repositories (clone + push + PR create) and write on issues (PR/issue
|
|
# comments). Read is implied by write. No admin/org/user-write scopes.
|
|
# Reading gitea/creds/teabot-implementer mints a lease-bound token deleted from
|
|
# Gitea on revoke/expiry.
|
|
---
|
|
username: teabot-implementer
|
|
scopes:
|
|
- write:repository
|
|
- write:issue
|
|
token_name_prefix: vault-teabot-implementer
|
|
ttl: 3600 # 1h
|
|
max_ttl: 14400 # 4h
|