Highlights
Server-side configuration validation
You can now run a server-side configuration validation using the adc validate. Essentially, this is equivalent to performing a dry-run synchronization.
All configurations are built as API requests and validated via the Admin API, allowing you to perform a more rigorous configuration validation than adc lint before actually running adc sync.
In terms of strictness:
adc sync > adc validate > adc lint
Now, the validate command is available on all backends.
In the future, we will also add a validate API to the adc server to improve the AIC user experience.
Enhanced error reporting
New binary ADC build, whose error call stack now reflects the original line and column numbers in the codebase. Previously, it could only display line numbers from the bundled JS file.
What's Changed
- fix(api7): make upstream optional by @jarvis9443 in #425
- test(api7): deploy test components by docker compose by @jarvis9443 in #429
- feat(cli): improve UX when throw error by @bzp2010 in #431
- feat(api7): add server-side configuration validator by @jarvis9443 in #432
- feat(cli): refine validate command by @bzp2010 in #433
- feat(apisix): add server-side configuration validator by @jarvis9443 in #434
- chore: upgrade dependencies by @bzp2010 in #435
- feat: bump to 0.25.0 by @bzp2010 in #436
New Contributors
- @jarvis9443 made their first contribution in #425
Full Changelog: v0.24.3...v0.25.0