How to validate json configuration files before deployment
- Step 1Paste the configuration file content — Copy the full content of the JSON configuration file: app.config.json, appsettings.json, cloudformation.json, or a Terraform *.tfvars.json file.
- Step 2Validate before committing — Click Validate. A green result means the file is syntactically valid JSON. An error result shows the exact position of the problem — go to that line and character in your editor to fix it.
- Step 3For JSONC files (tsconfig.json, .eslintrc.json) — Enable permissive mode to handle JSON with Comments syntax. These files use // comments and trailing commas that standard JSON validators reject.
- Step 4Add to your deployment checklist — Make JSON validation a step in your deployment runbook: validate all modified config files before running the deployment. CI validation (Step 10 above) automates this, but a manual pre-check catches errors before pushing.
Frequently asked questions
What are the most common JSON syntax errors in configuration files?+
The most common errors in hand-edited JSON config files: (1) trailing comma after the last element in an object or array, (2) missing comma between elements, (3) using single quotes instead of double quotes for strings, (4) unescaped backslashes in file paths (use \\ instead of \), (5) comments (// or /* */) in standard JSON files.
How do I validate Kubernetes JSON manifests?+
For syntax validation: paste the JSON manifest here. For schema validation against the Kubernetes API spec, use kubeval: kubeval my-manifest.json --schema-location=... or use kubeconform, which has built-in schema support. kubectl apply --dry-run=client -f manifest.json also performs validation against the connected cluster's API.
Are configuration files transmitted to JAD Apps?+
No. Validation runs entirely in your browser. Configuration file content including private settings and infrastructure definitions are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.