Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Small Bug: API Version on Connections page does not change when Kong is upgraded. #146

Closed
jeremyjpj0916 opened this issue Dec 6, 2017 · 5 comments
Labels

Comments

@jeremyjpj0916
Copy link
Contributor

The auto detected connections kong version is static, so while you may upgrade your kong connection version, this page will not detect that and leaves it at the original version the detection code must have seen originally. Needs to do a quick-check when that page loads to get the latest version and compare to current and update it if needed.

@pantsel pantsel added the bug label Dec 6, 2017
@jeremyjpj0916
Copy link
Contributor Author

To update this, it actually will auto update the number is you switch one admin api endpoint active from starred one back to it, aka unstar and then star it again. So it sort of auto updates? Just not in the context of doing the check without user intervention I suppose haha.

@pantsel
Copy link
Owner

pantsel commented Mar 2, 2018

@jeremyjpj0916 ,
As a temp workaround, the node version can be updated if you disable-reenable it from the connections page.

@jeremyjpj0916
Copy link
Contributor Author

Right yeah I had noticed that behavior, not too shabby :).

@pantsel
Copy link
Owner

pantsel commented Mar 3, 2018

@jeremyjpj0916 ,

this issue is fixed in v0.10.2.

Feel free to reopen if things are not working as expected.

@pantsel pantsel closed this as completed Mar 3, 2018
@jeremyjpj0916
Copy link
Contributor Author

Glad to see you back in action bud!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants