Nxtgauge GitOps Configuration
c559feea18
All checks were successful
sync-to-forgejo / sync (push) Successful in 15s
The previous B2_ACCESS_KEY_ID used the account's master-key ID (a raw
12-char account ID), which the B2 S3-compatible endpoint rejects with
403 InvalidAccessKeyId ("Malformed Access Key Id") even though it
authenticates fine against B2's native API. This was the root cause of
document uploads failing with a 500. Replaced with a properly scoped
Application Key generated for the Nxtgauge-object bucket, verified
against the live S3 endpoint (put/get/delete all succeed).
|
||
|---|---|---|
| .github/workflows | ||
| apps | ||
| clusters/production | ||
| docs | ||
| ops | ||
| scripts | ||
| .ci-trigger | ||
| .sops.yaml | ||
| .test_push | ||
| OTP_ISSUE_FIX_PROMPT.md | ||
| ROUTE_ISSUE_ANALYSIS.md | ||