Env Parity Checker
Dispatch Surface
Target: Agent Teams
Overview
Automated local-Docker vs onex-dev k8s parity checker. Detects:
- CRITICAL (default): credential drift, stale ECR tags, missing Infisical paths
- WARNING (--all-checks): schema drift, missing deployments, feature flag mismatches, Kafka topic gaps, package version mismatches
Incident origin (2026-03-10):
omniintelligence-credentials had POSTGRES_USER=postgres instead of role_omniintelligence — DB auth failures after pod restart
- ECR tags deleted while still referenced in active deployment specs —
ErrImagePull on rollout
- Infisical paths never seeded — InfisicalSecret 404 loops for hours
The onex:gap skill covers code/contract drift. This skill fills the runtime state gap.
Checks Catalog
| check_id |
severity_tier |
incident_class |
default |
auto_fixable |
credential |
CRITICAL |
DB auth failure on pod restart |
yes |
no |
ecr |
CRITICAL |
ErrImagePull on rollout |
yes |
no |
infisical |
CRITICAL |
InfisicalSecret 404 loops |
yes |
yes |
schema |
WARNING |
Migration state drift |
--all-checks |
no |
services |
WARNING |
Missing deployment |
--all-checks |
no |
flags |
WARNING |
Feature flag inconsistency |
--all-checks |
no |
kafka |
WARNING |
Missing Kafka topics in cloud |
--all-checks |
no |
packages |
WARNING |
Package version mismatch |
--all-checks |
no |
When to Use
- Post-incident: After any DB auth failure, ErrImagePull, or InfisicalSecret error
- Pre-deploy: Before promoting a new release to verify cloud state matches local
- Ad hoc: When suspecting drift between local and cloud environments
Quick Start
# Default: CRITICAL checks only (credential, ECR, Infisical) and ticket CRITICAL findings
/env-parity check
# All 8 checks
/env-parity check --all-checks
# Fix Infisical path gaps (only auto-fixable check)
/env-parity fix --checks infisical
# Dry-run fix
/env-parity fix --checks infisical --dry-run
# Explicitly request ticket creation (also the default)
/env-parity check --create-tickets
# Disable ticket creation for a read-only parity check
/env-parity check --no-create-tickets
Alert Thresholds
| Severity |
Action |
| CRITICAL |
Fix today — active or imminent production impact |
| WARNING |
Fix this sprint — quality/reliability risk |
| INFO |
Informational — no action required |
Ticket Creation
Linear ticket creation is enabled by default for CRITICAL findings so active env
mismatches are tracked. Pass --no-create-tickets for explicit read-only runs.
--create-tickets remains accepted for callers that want to be explicit.
When ticket creation is enabled, one ticket is created per CRITICAL finding using:
- Title:
[env-parity:<check_id>] <finding title verbatim>
- Priority: 1 (Urgent)
- Project: Active Sprint
- Deduplication: exact prefix match on
[env-parity:<check_id>] — skip if any existing ticket (any state) matches
See Also
system-status — overall platform health check
gap — code/contract drift detection
omnibase_infra/scripts/system_health_check.sh — infrastructure health
omnibase_infra/scripts/compare_environments.py — the underlying probe script
1---2name: env-parity3description: Local Docker vs onex-dev k8s environment parity checker -- dispatches to node_env_parity_compute for execution4mode: full5version: 1.0.06level: advanced7debug: false8category: operations9tags: [parity, drift, credentials, ecr, infisical, k8s, docker]10author: OmniClaude Team11composable: true12inputs:13 - name: subcommand14 type: str15 description: "Mode: check (audit) or fix (auto-fix Infisical paths only)"16 required: false17args:18 - name: subcommand19 description: "Mode: check (default) or fix"20 required: false21 - name: --checks22 description: "Comma-separated check IDs (default: credential,ecr,infisical)"23 required: false24 - name: --all-checks25 description: "Run all 8 checks including secondary (schema, services, flags, kafka, packages)"26 required: false27 - name: --namespace28 description: "k8s namespace to probe (default: onex-dev)"29 required: false30 - name: --dry-run31 description: "Preview fix actions without executing"32 required: false33 - name: --create-tickets34 description: "Create Linear tickets for CRITICAL findings. Default: true (on-by-default; pass --no-create-tickets to disable)"35 required: false36 - name: --no-create-tickets37 description: "Do not create Linear tickets for CRITICAL findings"38 required: false39metadata:40 source: https://skillmd.com/skills/omninode-ai/env-parity41---4243<!-- routing-enforced: dispatches to node_env_parity_compute. -->4445# Env Parity Checker4647## Dispatch Surface4849**Target**: Agent Teams5051## Overview5253Automated local-Docker vs onex-dev k8s parity checker. Detects:5455- **CRITICAL** (default): credential drift, stale ECR tags, missing Infisical paths56- **WARNING** (--all-checks): schema drift, missing deployments, feature flag mismatches, Kafka topic gaps, package version mismatches5758**Incident origin (2026-03-10):**591. `omniintelligence-credentials` had `POSTGRES_USER=postgres` instead of `role_omniintelligence` — DB auth failures after pod restart602. ECR tags deleted while still referenced in active deployment specs — `ErrImagePull` on rollout613. Infisical paths never seeded — InfisicalSecret 404 loops for hours6263The `onex:gap` skill covers code/contract drift. This skill fills the runtime state gap.6465## Checks Catalog6667| check_id | severity_tier | incident_class | default | auto_fixable |68|----------|--------------|----------------|---------|-------------|69| `credential` | CRITICAL | DB auth failure on pod restart | yes | no |70| `ecr` | CRITICAL | ErrImagePull on rollout | yes | no |71| `infisical` | CRITICAL | InfisicalSecret 404 loops | yes | yes |72| `schema` | WARNING | Migration state drift | --all-checks | no |73| `services` | WARNING | Missing deployment | --all-checks | no |74| `flags` | WARNING | Feature flag inconsistency | --all-checks | no |75| `kafka` | WARNING | Missing Kafka topics in cloud | --all-checks | no |76| `packages` | WARNING | Package version mismatch | --all-checks | no |7778## When to Use7980- **Post-incident**: After any DB auth failure, ErrImagePull, or InfisicalSecret error81- **Pre-deploy**: Before promoting a new release to verify cloud state matches local82- **Ad hoc**: When suspecting drift between local and cloud environments8384## Quick Start8586```bash87# Default: CRITICAL checks only (credential, ECR, Infisical) and ticket CRITICAL findings88/env-parity check8990# All 8 checks91/env-parity check --all-checks9293# Fix Infisical path gaps (only auto-fixable check)94/env-parity fix --checks infisical9596# Dry-run fix97/env-parity fix --checks infisical --dry-run9899# Explicitly request ticket creation (also the default)100/env-parity check --create-tickets101102# Disable ticket creation for a read-only parity check103/env-parity check --no-create-tickets104```105106## Alert Thresholds107108| Severity | Action |109|----------|--------|110| **CRITICAL** | Fix today — active or imminent production impact |111| **WARNING** | Fix this sprint — quality/reliability risk |112| **INFO** | Informational — no action required |113114## Ticket Creation115116Linear ticket creation is enabled by default for CRITICAL findings so active env117mismatches are tracked. Pass `--no-create-tickets` for explicit read-only runs.118`--create-tickets` remains accepted for callers that want to be explicit.119120When ticket creation is enabled, one ticket is created per CRITICAL finding using:121- Title: `[env-parity:<check_id>] <finding title verbatim>`122- Priority: 1 (Urgent)123- Project: Active Sprint124- Deduplication: exact prefix match on `[env-parity:<check_id>]` — skip if any existing ticket (any state) matches125126## See Also127128- `system-status` — overall platform health check129- `gap` — code/contract drift detection130- `omnibase_infra/scripts/system_health_check.sh` — infrastructure health131- `omnibase_infra/scripts/compare_environments.py` — the underlying probe script