Skip to content

Configra v1.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Oct 11:33
· 0 commits to main since this release
v1.1.0
5bd686a

Automation can now write Config and Vault resources in explicit environments and
issue/revoke read-only deployment Token/client-certificate pairs through the
9443 machine API. Scoped writers require both Token and a registered active
mTLS certificate; only an OIDC Administrator with verified signed MFA evidence
can issue them on Management. Environment creation, user/role administration,
writer delegation and Master Key export remain outside this credential's powers.

新增有范围的写令牌：管理员在管理端 OIDC 登录并提供签名 MFA 证明后签发，绑定环境、
可选 Config/namespace 白名单，明确过期（默认最多 90 天，可配置更短）并可随时吊销。
9443 同时校验 Token 与 mTLS 证书，支持范围内 Config 版本、Vault item/field/File
写入，以及继承范围的只读部署 Token/证书签发与吊销。全部写操作记录无值审计，包含
Token ID、操作、对象/字段、时间、来源 TCP IP；部署凭据与证书绑定，writer 吊销会级联。

Upgrade from v1.0.1 requires a maintenance window: stop all replicas/workers,
back up MySQL/ClickHouse and preserve the original Master Key. Start one new
Management replica first to migrate MySQL schema 2 → 3 and add ClickHouse
Audit source_ip/field_key; verify readiness/schema before starting other new
replicas and API. API now needs runtime database write privileges but does not
perform migrations. Configure signed IdP amr MFA evidence and log in again.
Existing read-only credentials remain compatible. Rollback requires restoring
the complete pre-upgrade backup and original key; mixed binaries or stripping
scope columns are unsupported.

升级必须安排维护窗口并备份，保留原 Master Key；先启动一个新版 Management 自动迁移
MySQL schema 2→3 和 ClickHouse 审计列，验证后再启动其余副本与 API。API 账号需要
运行时写权限，API 不执行迁移。配置 IdP 签名 amr MFA 并重新登录。旧只读凭据保留；
回退恢复完整升级前备份与原密钥，不能混跑旧版本或原地删除 scope 列。

Verification / 验证

  • Server PR CI and
    SDK CI.
  • Real MySQL 8.0.22/NATS/ClickHouse/HTTPS/mTLS E2E exercises scope 403s,
    expiry/revocation, retained history, audit metadata/redaction and the actual
    SDK operator uploading 17 secret File fields in both testing and production.
  • The unchanged ten-minute Mac/Docker capacity gate passes with 600,000 /
    600,000 HTTP 200    , 999.996 completed/s, p99 24.911 ms and all 615,002 Access
    Events captured/persisted, API limited to 2 CPUs / 512 MiB. Leakage scans
    pass. Three-node Kubernetes acceptance also passes.
  • The bounded evidence record
    retains the earlier 34 local timeouts and hosted Linux warmup failure; this
    release does not claim new native Linux capacity acceptance or a deployment SLA.

Release source: 5bd686a23feeda93527b217a59e56811da888140;
server PR #14 and
SDK PR #3.
Runtime acceptance used d06c1851b163f431bf21e0382cd9cd04d2d130f2; the subsequent
commit changes only release/verification documentation.

Downloaded draft archives independently pass all four SHA256 checks, executable target/toolchain checks, complete runtime/module/UI license and source materials, and SBOM/inventory binding. Darwin bundles each contain 269 inventoried files / 120 components; Linux bundles each contain 271 files / 121 components. All BUILD records map to the release source above; native arm64 Configra and Kubernetes executables report v1.1.0 and that commit. Tagged release build also passes Linux binary execution. SDK v1.1.0 is independently downloaded through the official Go proxy/sumdb; its published module checksum is h1:d/vkzh9iVLGgOpLNuOEp0Z2z93p6B3txPZAjPQVzLrg=.

SHA256SUMS:

1ffb0decb2e24f313a063afe3c94bf7d98289bdcb6f5ed2df5134c9186cc4f6f  configra_1.1.0_darwin_amd64.tar.gz
6fb55e4db123bae6853a1e02b7717a54e5b1687d6d798d98d2cbb2868da735b6  configra_1.1.0_darwin_arm64.tar.gz
95b2621a32ec763cdf213e000a86c0662483fbd9765dbd23ada35ff8a7cfcf7a  configra_1.1.0_linux_amd64.tar.gz
8d8b091c4af851d8960c419e6acd8279d78b9731b649b82b34d9ca64fb401a64  configra_1.1.0_linux_arm64.tar.gz
Assets 7
Loading