Skip to content

Release v0.0.329

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Sep 11:04
· 75 commits to main since this release
v0.0.329
e0a17ee
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

  • Live-validated all 11 Custom<Resource>RestEnabled flags against real data on armo-dev-stage (2026-08-31) — zero behavioral divergence found between the old genericregistry.Store implementations and the new genericrest.Store-based ones (see docs/features/generic-rest-storage-phase4.md, -containerprofile.md, -remaining-resources.md).
  • The 11 flags keep defaulting to false. An earlier version of this PR flipped the code-level default to true; that was reverted, since a single cluster's validation isn't grounds to silently switch every deployment of this binary — only the ones that explicitly opt in.
  • New: a single CUSTOM_REST_ENABLED env var (pkg/config.CustomRestEnabledEnvVar) overrides all 11 flags at once when set, regardless of config.json. The 11 individual flags stay as our own fine-grained per-resource rollback mechanism; this env var is for deployments — notably design-partner test environments — that want one on/off switch instead of 11 config.json fields to learn. See docs/features/custom-rest-enabled-env-var.md.
  • configuration/config.json (this repo's own local/test config) sets none of the 11 keys, so it's unaffected either way.

Test plan

  • go build ./...
  • go test ./... full suite green
  • TestLoadConfig confirms the 11 flags default to false (unchanged from before this PR)
  • TestCustomRestEnabledEnvVar (new): unset leaves a mixed config.json's per-resource values untouched; "true"/"false" override every flag regardless of config.json; an invalid value errors loudly. Confirmed discriminating (doesn't compile without the fix).

🤖 Generated with Claude Code

https://claude.ai/code/session_01AjRp2JR5NuhdqAnpVBwReC

Assets 2
Loading