API gateways are crucial for ensuring the security, availability, and responsiveness of APIs, and maintaining robust gateway configurations is essential. The decK 1.28 update introduces a new feature that enables native validation of gateway configurations against custom rule sets, enhancing compliance with best practices and fortifying gateway deployments. This feature integrates linting capabilities, a process often used to detect potential errors and deviations from coding standards, directly into the decK command line tool, facilitating seamless integration with CI/CD pipelines. The deck file lint command functions as a flexible JSON/YAML linter, enabling users to create rules that filter and validate file contents using JSONPath syntax. It allows for defining severity levels and output formats, adding versatility to the command. For example, users can ensure that only secure https protocols are used in Kong Gateway configurations by applying a specific ruleset. The command's success or failure is indicated by return codes, which help in aborting processes if violations are detected, thus preventing problematic configurations from reaching production environments. The implementation relies on the GoLang-based Vacuum library, and further documentation and examples are available for APIOps and Kong-specific use cases, with additional resources accessible through the Kong Konnect platform.