Redis ConfigHub Function Scan Lane

Purpose

Acceptance Contract

Accepted when:

• the scan runs against ConfigHub Units, not only local files;
• the selected Units are the Redis Units from the helm-redis-confighub-proof proof space;
• every scanned Unit is bound by HeadRevisionNum and DataHash;
• at least three current validating functions pass;
• failures or missing executors are recorded as blockers, not hidden.

Run

Run date: 2026-05-27

Context:

Organization: Kubara
Server: https://hub.confighub.com
Space: helm-redis-confighub-proof
Selector: Labels.Proof = 'redis-confighub-proof'

Commands:

New to cub? Install the cub CLI first. Public catalog packages pull and render anonymously, and you sign in only once a command saves or changes ConfigHub data.

CUB_CONFIG=$HOME/.confighub/config.yaml cub function vet vet-format \
  --space helm-redis-confighub-proof \
  --where "Labels.Proof = 'redis-confighub-proof'" \
  --output json \
  --wait

CUB_CONFIG=$HOME/.confighub/config.yaml cub function vet vet-placeholders \
  --space helm-redis-confighub-proof \
  --where "Labels.Proof = 'redis-confighub-proof'" \
  --output json \
  --wait

CUB_CONFIG=$HOME/.confighub/config.yaml cub function vet vet-merge-keys \
  --space helm-redis-confighub-proof \
  --where "Labels.Proof = 'redis-confighub-proof'" \
  --output json \
  --wait

Result:

Receipt:

runs/redis-confighub-proof/latest/function-scan-receipt.yaml

Interpretation

This proves current ConfigHub functions can scan the uploaded Redis Units in place. It is deliberately modest: these checks catch real apply and review hazards, but they do not claim full production security approval.

Production readiness still needs the external scanner and policy disposition already represented by the Redis recipe scan and install gate.