bao-kms-providerSearch GitHub

Development

These pages cover local development, CI, release process, and how the docs site is built. Use them as a contributor or reviewer rather than as an operator.

Topics

  • Contributing for local environment setup, Go version, and the contribution workflow.
  • Code Quality for the strict typed Go conventions, ast-grep rules, and Semgrep boundaries.
  • Testing for the unit, integration, and end-to-end testing strategy.
  • E2E Framework for runnable E2E lane commands, labels, manifest routing, and reports.
  • Performance Evidence for captured load, cold-start, and recovery results.
  • CI And Supply Chain for the CI pipeline, version pinning, and supply-chain controls.
  • Docs Style Guide for writing, structure, linking, and docs verification guidance.
  • Docs Site for how this Hugo site is structured, built, and published.

Use Another Section If

  • the question is about installing, wiring, or operating the provider: go to Start Here or Operations .
  • the question is about exact CLI, configuration, or contract behavior: go to Reference .
  • the question is about the design rationale behind a feature: go to Architecture .

Browse

In This Section

Contributing Repository layout, local development setup, test expectations, code quality rules, wire compatibility commitments, and documentation update policy for bao-kms-provider contributors. Code Quality Strict typed Go conventions, ast-grep architecture rules, Semgrep security rules, package boundaries, and required quality gates for bao-kms-provider. Testing Testing strategy for bao-kms-provider: protocol correctness, fail-closed behavior, rotation, recovery, performance, and release evidence. E2E Framework Runnable E2E lanes, label routing, suite manifest, environment variables, reports, and artifacts for bao-kms-provider. Performance Evidence Captured load, decrypt warmup, and kubeadm cold-start evidence used for release decisions. CI And Supply Chain Version pinning, CI lanes, release automation, artifact signing, provenance, reproducibility, and release evidence for bao-kms-provider. Docs Style Guide Writing, structure, linking, and verification guidance for the published documentation. Docs Site How the Hugo documentation site is organized, built, checked, and published.