Kong1dot1
Splits /apis endpoint into /routes and /services that Kong 1.0 introduced. We're running this fine for 6 months now. First Kong 1.1, currently Kong 1.4
I split off the Travis and rubocop fixes into separate PRs.
@mtmail @nevalla This is a very useful PR. Is there anything blocking this?
@mtmail if you are using this rt now, is there a gem version published somewhere?
@mtmail i was not able to add upstreams for using this and getting
Kong::Error ({"message":"schema violation (upstream_id: unknown field)","name":"schema violation","fields":{"upstream_id":"unknown field"},"code":2})
the docs show target structure has changed https://docs.konghq.com/1.4.x/admin-api/#add-target
@mtmail
This is a workaround i am doing to make this work https://github.com/irfn/kong-client-ruby/commit/a0ee5914d96f5894a03024b5a4356d7fe3101f46 hope you can address this.
Actually ignore the above workaround. It only allows you to create and not view. Here i have updated this to handle update & view (still workaround quality)
https://github.com/irfn/kong-client-ruby/commit/758974e464665695c5214da4760fd9c1e05384ac
@mtmail @irfn sometimes it seems like this gem is not being maintained anymore, but I'm not sure. Did you publish your fork publicly in the Rubygems?
Do you intend to maintain a fork to let it updated with new Kong versions? I'm interested to help.
Hi, sorry for not giving any feedback here. Finally, I have now time to push this further. So, I'll test this out with the latest version of Kong and review the PR.
After we get this merged I'll create a beta/rc build so you can test it too.
Please could you rebase and resolve conflicts. Meta PRs are now merged so it would be easier to review this PR.
I split off the bundler,rake changes into a separate PR https://github.com/kontena/kong-client-ruby/pull/42
@mtmail do you intend to work on Kong 1.4.x support? I mentioned the issue in the thread.
@irfn I'm using this library with 1.4.0 already, I guess not the feature you mention. Can you create a separate github issue?
Rebased, squashed, and tests passing. I set version to 0.4.0 and added a changelog entry.
@irfn I'm using this library with 1.4.0 already, I guess not the feature you mention. Can you create a separate github issue?
Ill retest and raise issue once this is merged. thanks!
Any update?
We are really looking forward to use Kong::Service and working Kong::JWT :)
My fork works with Kong 2.x