This repository has been archived by the owner on Jul 8, 2022. It is now read-only.
Releases: justeat/kongverge
Releases · justeat/kongverge
3.1.0
- Added support for syncing consumers (via a new child collection property in the
global.json
config file) - Enable matching objects by predicate, allowing sync to be based on
Id
property matches if provided in config files. - Added support for ignoring objects having specified tag(s) when reading from Kong.
3.0.1
Fixed bugs introduced by migration to new Kong schema validation:
- Fixed faulty type checking and null/default value handling
- Switched to using
PUT
verbs for creating/updating allKongObject
s via the Admin API, including support for client generatedId
s in config objects - Fixed Kong version gate so that it blocks usage on versions lower than
1.4.0
3.0.0
Updates to Kongverge to support Kong versions as follows:
- Kong version
1.4.x
and above - Kong Enterprise Edition version
0.36-x
and above
Various updates, including:
- Changes to Add/Update
KongPlugin
via Admin API - Schema changes for
KongService
,KongRoute
,KongPlugin
- New unimplemented
KongConsumer
andKongCertificate
classes - Changes to equality checking and
ToSring()
implementations for all objects derived from abstractKongObject
- Refactored schema validation logic into
KongSchema
class and standardize all validation to use schema objects
Updated the gate for version compatibility so that we can't support the following versions:
- Kong between version
0.15.x
and1.3.x
(inclusive) - Kong Enterprise Edition version
0.35-x
2.0.6
Added version compatibility check and exit if not compatible. This version of Kongverge can only support:
- Kong up to version
0.14.x
and - Kong enterprise up to version
0.34-x
.
2.0.5
- Removed fault-tolerance
- Improved logging output to always mention the kong host being targeted
- Updated NuGet packages
- Updated target framework to netcoreapp2.2
2.0.3
Added array type-checking to plugin schema validation.
2.0.2
Added validation to ensure service names are unique.
2.0.1
Improved validation of route paths to require that they begin with a forward slash (/
).
2.0.0
Added support for authenticating against the Kong Admin API using Basic Authentication.
Some breaking changes were made in this release:
- The command-line arguments are parsed differently. We now have three actual commands that can be specified on the command-line (
run
/dry-run
/export
). The options which apply to all commands (--host
,--port
,--user
,--password
) need to be specified first, followed by one of the commands, and then any arguments to that command.run
anddry-run
require an unnamed argument specifying the input folder.export
requires an unnamed argument specifying the output folder.--host
is always required.--port
is optional and defaults to8001
.--user
and--password
are optional, but need to either both be specified or both be absent. The--password
option allows passing the value from redirectedstdin
. - A previously undocumented feature for reading the command-line options from environment variables has been removed.
- The exit codes have changed to:
0
- Success1
- Unspecified error (with error message output to console)2
- Host unreachable (with error message output to console)3
- Input folder unreachable (with error message output to console)4
- Invalid configuration files(s) (with error message output to console)
1.2.0
Includes the following significant changes:
- Removed extra square brackets from
KongRoute.ToString
method output - Prefixed
KongService
validation error messages with "Service" - Verbose console output displays a link to Delta Format if there were any updates
- Added
KongPlugin.Config
schema validation and defaults substitution to avoid false positives (differences that aren't really differences) and thus clean up console output and avoid sending updates to Kong that won't have any effect