You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 2.x and 3.x target endpoints are mutually incompatible after https://github.com/Kong/kong/pull/8596/files. There are no options to for a single piece of code that supports both, even if we drop support for older 2.x versions, as there are no 2.x releases that support PUT.
This requires either version-dependent code within the function or separate 2.x and 3.x functions. AFAIK we have no existing pattern for this in go-kong, as other version-dependent behavior is not part of the API (or is limited to fields that only exist in newer versions, which can coexist fine in the schemas) and delegated downstream.
The text was updated successfully, but these errors were encountered:
@pmalek we're in the process of upgrading kong to 3 latest which requires patch for target update admin APIs. Code here still supports only post. any update here?? Thanks in advance.
As far as I can tell, we can easily introduce version dependent code by checking the version in NewClient() via .Info service and then use that in TargetService.
The 2.x and 3.x target endpoints are mutually incompatible after https://github.com/Kong/kong/pull/8596/files. There are no options to for a single piece of code that supports both, even if we drop support for older 2.x versions, as there are no 2.x releases that support PUT.
This requires either version-dependent code within the function or separate 2.x and 3.x functions. AFAIK we have no existing pattern for this in go-kong, as other version-dependent behavior is not part of the API (or is limited to fields that only exist in newer versions, which can coexist fine in the schemas) and delegated downstream.
The text was updated successfully, but these errors were encountered: