0.17.0

Highlight

Support for multi-file input using glob

This has been implemented on the diff and sync commands. It is not implemented on OpenAPI Converter because it doesn't support multi-file input yet, which will be improved later.

It now supports such syntax:

• adc sync -f 'spec/*.yaml'
• adc sync -f 'spec/**/*.yaml'

Note that the glob expressions need to be quote-wrapped because we don't want the glob implementation in the shell to intervene for a uniform user experience.

More guides: https://github.com/isaacs/node-glob?tab=readme-ov-file#glob-primer

APISIX support down to 3.2.x

APISIX support has been extended to 3.2, which was an LTS but is now considered retired, which helps users to migrate.

For Known Issues/Limitations, please refer to: https://github.com/api7/adc/blob/main/libs/backend-apisix/README.md

What's Changed

• feat(core): support glob file path by @bzp2010 in #212
• feat(apisix): support apisix lower than 3.8 by @bzp2010 in #213
• feat(core): dump sorted yaml by @bzp2010 in #217
• feat(api7): support route vars expr by @bzp2010 in #219
• fix(apisix): service missing hosts by @bzp2010 in #220
• feat: bump to 0.17.0 by @bzp2010 in #221
• fix(apisix): upstream nodes should be allowed to be null by @bzp2010 in #222
• docs(api7): add 3.3.x support by @bzp2010 in #223

Full Changelog: v0.16.2...v0.17.0

0.16.2

What's Changed

• feat: release docker image by @bzp2010 in #209
• feat: bump to 0.16.2 by @bzp2010 in #210
• fix: docker release tag typo by @bzp2010 in #211

Full Changelog: v0.16.1...v0.16.2

0.16.1

What's Changed

• feat(core): loose custom resource id length by @bzp2010 in #206
• feat: bump to 0.16.1 by @bzp2010 in #207

Full Changelog: v0.16.0...v0.16.1

0.16.0

Highlight

Support for custom resource ID

The resource ID can now be customized by the user instead of letting ADC generate it automatically.
Just write the id field in the resource to make it work, but there are a few resources that are not supported yet, such as upstream (which is inlined by the service and doesn't support references) and consumer (whose username is the ID and doesn't want to be specified additionally).

It has been implemented on API7 and APISIX. #203 #204

What's Changed

• fix(api7): mismatched fields in upstream mtls by @bzp2010 in #202
• feat: support custom resource id by @bzp2010 in #203
• feat(core): update custom id schema by @bzp2010 in #204
• feat: bump to 0.16.0 by @bzp2010 in #205

Full Changelog: v0.15.0...v0.16.0

v0.15.0

Highlight

Support for Consumer Credentials on Apache APISIX✨

This release supports consumer credentials on APISIX, which will be enabled after APISIX is upgraded to 3.11.0. If not, you can only use the legacy consumer plugins format.

What's Changed

• feat: output more logs when errors happened by @bzp2010 in #187
• feat(api7): allow mutliple uris in route by @bzp2010 in #191
• feat(api7): support route-level timeout by @bzp2010 in #197
• chore: upgrade nx toolchain by @bzp2010 in #198
• test(api7): fix consumer credentials by @bzp2010 in #199
• feat(apisix): support consumer credentials by @bzp2010 in #200
• feat: bump to 0.15.0 by @bzp2010 in #201

Full Changelog: v0.14.0...v0.15.0

v0.14.0

Highlight

Support for Consumer Credentials✨

This release supports consumer credentials on API7, which will be enabled after API7 is upgraded to 3.2.15. If not, you can only use the legacy consumer credentials format.

What's Changed

• fix(core): re-order ssl operation events by @bzp2010 in #183
• feat(core): improve oas converter error output by @bzp2010 in #184
• feat(api7): support consumer credentials by @bzp2010 in #182
• feat: bump to 0.14.0 by @bzp2010 in #186

Full Changelog: v0.13.0...v0.14.0

v0.13.0

NOTICE

From this release, ADC will drop API7 3.2.13.0 support in favor of new features that became available on API7 3.2.14.x.

---

What's Changed

• feat(core): looser name length by @bzp2010 in #179
• feat(api7): add priority support by @bzp2010 in #170
• feat: bump to 0.13.0 by @bzp2010 in #180

Full Changelog: v0.12.2...v0.13.0

v0.12.2

What's Changed

• ci: test api7 on 3.2.14.3 by @bzp2010 in #167
• fix(core): route vars expr schema by @bzp2010 in #168
• fix(core): upstream health checker optional field schema by @bzp2010 in #169
• fix: improve inline documentation by @pottekkat in #172
• feat: add inline examples by @pottekkat in #174
• feat(core): linter looser description length by @bzp2010 in #175
• feat: bump to 0.12.2 by @bzp2010 in #176

Full Changelog: v0.12.1...v0.12.2

v0.12.1

What's Changed

• docs: update installation instructions in readme by @pottekkat in #161
• fix(core): upstream linter check either nodes or service discovery by @bzp2010 in #163
• fix(core): ssl secret ref by @bzp2010 in #164
• feat: bump to 0.12.1 by @bzp2010 in #165

Full Changelog: v0.12.0...v0.12.1

v0.12.0

Announcing the release of a NEW API Declarative CLI (ADC)

Six months have passed since the last release, and a lot has changed in the ADC.

Because the previous developers never considered the project's extensibility, we had trouble adding new features and maintaining them continuously. For example, we needed help adding support for our enterprise product, API7 Enterprise. The old ADC was deeply coupled to the APISIX Admin API.

Also, ADC was being developed in Go at that time. While it had some advantages in cross-compilation, developers had to waste more time writing boilerplate code such as structs. Boilerplate codes waste a lot of time, and the developer could have spent using their talents to create outstanding functionality.

This state of affairs must be improved or the ADC project cannot continue.

So, thanks to the efforts of several developers, we rewrote every line of code and added more new features that users have come to expect.

The new codebase was developed in TypeScript, a brilliant language that allows for more creativity than Go, which allowed us to do more with fewer lines of code.

We have developed and released many versions internally, but as I mentioned at https://api7.ai/blog/adc-0.7-and-api7 and https://api7.ai/blog/adc-0.8-0.9-0.10, it will eventually be released as an open source project.

From now on, it will be developed and released publicly. Version numbers will jump from 0.5.2 to 0.12, and you can check out the new features we've introduced via the two blogs mentioned above.

Full Changelog: v0.5.2...v0.12.0