Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Kong 0.10 #2

Merged
merged 3 commits into from Apr 11, 2017

Conversation

brothhaar
Copy link
Contributor

Added support for Kong 0.10. This included changes to api
validation to support backwards incompatible field changes. Also
added a package config kongVersion. This is currently defaulted
to 0.9 but can be set bynpm config set kingkong:kongVersion 0.10
to test against other Kong versions. Tests are configured to use
kongVersion as part of the spec file name.

Added support for Kong 0.10. This included changes to api
validation to support backwards incompatible field changes. Also
added a package config `kongVersion`. This is currently defaulted
to `0.9` but can be set by`npm config kingkong:kongVersion 0.10`
to test against other Kong versions. Tests are configured to use
`kongVersion` as part of the spec file name.
Copy link
Owner

@esatterwhite esatterwhite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather not try to support every breaking change to kong. We have semver for that. Lets just drop the old 0.9 code and get rid of the npm config stuff

@@ -14,9 +14,12 @@ var joi = require('joi')
module.exports = joi.object({
name: joi.string()
, request_path: joi.string().optional()
, uris: joi.array().items(joi.string().optional())
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If 0.9 and 0.10 don't have a compatible API, I don't think this project should try to maintain compatibility with breaking changes in the project.

Someone could Have 0.10 Kong instance running and make a valid 0.9 request.

I'd much rather follow suite: just make the changes required to work with 0.10, disregard 0.9. I'll just publish a new major version.

I can set up CI to run on a tag for each Kong version. Less cruft in the code, less prone to user error and easier to deal with.

Mind just removing the old 0.9 stuff?

Thanks!

@brothhaar
Copy link
Contributor Author

@esatterwhite Good call. I removed the 0.9 compatibility.

@esatterwhite esatterwhite merged commit 1ec2193 into esatterwhite:master Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants