The current XL CLI behavior during apply failures is insufficient for debugging and automation workflows. When a YAML error occurs, the CLI only returns a generic message such as:
Error in line 1 of yaml


This lack of detailed logging significantly hampers troubleshooting, especially in automated pipelines where manual intervention should be minimized.
Problem Statement:
- The CLI does not provide line-specific context or stack traces for YAML parsing errors.
- Automation workflows using XL CLI are disrupted due to vague error messages.
- Manual debugging becomes necessary, increasing operational overhead and reducing deployment velocity.

Proposed Enhancement:
Introduce a verbose logging mechanism in XL CLI that includes:
- Precise line and column numbers of the YAML error
- Description of the parsing issue (e.g., unexpected token, missing key)
- Optionally, a snippet of the problematic YAML section
- A --verbose or --debug flag to toggle detailed output

Benefits:
- Faster root cause analysis during CLI-driven deployments
- Reduced manual effort in CI/CD pipelines
- Improved developer experience and reliability of automation

This will be critical for teams leveraging XL CLI in production-grade automation.

by: Prashanth P. | about a day ago | API & CLI tools