CHECK_COMPAT(1)

💖 CHECK_COMPAT — the check_compat era 💖

okay bestie, so this is section 1 of the manual, and we're about to find out if ur conf2 YAML files are actually compatible or just pretending 🫶

---

✨ NAME ✨

check_compat — sniffs out incompatible configurations in conf2 module YAML files 🕵️♀️💅

---

🌸 SYNOPSIS 🌸

check_compat -o OUTPUT_FILE [-h]

that's it. that's the whole vibe. one required thing, one optional thing. slay.

---

🦋 DESCRIPTION 🦋

So like, this program scans conf2 module YAML files to find configurations that are, um, not compatible with each other. Not me being the compatibility police 😭

It runs validation checks against conf2 module specifications and then dumps all the issues it found into the results file you told it to use. iconic behaviour honestly.

---

🎀 OPTIONS 🎀

• -h, --help — shows u the help message and then exits. the classic "wait what does this do" move 💖
• -o OUTPUT_FILE, --output OUTPUT_FILE — tells it where to put the validation results. this one is REQUIRED, bestie, no skipping it 🚨

---

👑 OPERATION 👑

Here's the little routine it does, step by step, main character energy only:

1. Scans the current working directory and relevant system paths 🔍
2. Identifies conf2 module YAML configuration files 📂
3. Validates configurations against compatibility rules ✅
4. Writes detected issues to the specified output file 📝

---

🌈 OUTPUT FORMAT 🌈

The output file is giving:

• List of incompatible configurations 💀
• File paths where issues were detected 📍
• Specific configuration keys causing incompatibilities 🔑
• Severity level for each issue ⚠️

---

⭐ EXIT STATUS ⭐

• 0 — Success (no incompatible configurations found) 🎉 clean, no notes, we love to see it
• 1 — Validation errors detected 😭 something's incompatible, the drama
• 2 — Execution error (invalid parameters or system issues) 🚨 like, it couldn't even run properly

---

🧚 EXAMPLES 🧚

Basic usage:

check_compat -o validation_results.txt

Check exit status:

$ check_compat -o report.log
$ echo $?
1  # indicates issues found

see that 1? yeah that means issues were found. the vibe check failed fr fr 😔

---

🔥 SEE ALSO 🔥

conf2(1), yamllint(1)

go read those too, iykyk 💜

---

💅 DIAGNOSTICS 💅

The output file will contain stuff like this:

ERROR: Incompatible setting detected in /etc/conf2/app.yaml
Key: security.encryption_level
Current value: legacy
Required: modern

okay so lowkey this is the moment of truth — it literally tells u the file, the key, what u have, and what u need. no guessing required 🫶

---

🌸 AUTHOR 🌸

UKUI Quality Assurance Team — shoutout to them, they're doing the lord's work 👑

---

and that's the whole page, babe! this was v1.0, dated 2025-07-24, from the CHECK_COMPAT(1) manual — Configuration Validation section. now go forth and validate those YAMLs 💖✨🦋