What is authoritative?
Name the file or artifact consumed by deployment before comparing representations.
Elysia Tools
Navigation
Workflow Playbook
Inspect, validate, convert, merge, and diff configuration without exposing secrets or losing the source of truth.
Hubs
Start with the file or generated artifact the deployment actually consumes. Parse its keys and scalar types, replacing passwords, tokens, certificates, and private keys with placeholders. A readable diff is unsafe when it contains original values.
Check syntax, required keys, duplicate behavior, and layer precedence. YAML, JSON, TOML, HCL, properties, and environment formats differ in quoting, nulls, booleans, and repeated keys.
Merge deliberately, inspect deletions and type changes, revalidate the final artifact, and record the owner, source, conversion direction, and secret-handling decision.
Workflow playbook
Parse environment, properties, or SSH input and record keys, types, and redacted placeholders.
Check syntax, required entries, duplicate handling, and safe test values.
Convert YAML, JSON, TOML, or HCL, or merge YAML layers using documented precedence.
Review deleted keys, type changes, and defaults, then validate the final redacted artifact.
Name the file or artifact consumed by deployment before comparing representations.
Validate syntax and required keys before conversion, then validate the output.
Use stable placeholders in review and keep real values in the approved secret store.