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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Tyk Gateway 4.3.2
Fixed
Fixed an issue with the behavior of the Gateway when a plugin bundle fails to download, Tyk will now try a total of five times with increasing back off between attempts
Fixed an issue where the fix for TT-6668 was not applied to Response Handler plugins
Prevented logrus_sentry.NewSentryHook to return nil instead of a proper SentryHook handlerresponse, instead the response will be reused for multiple fields connected to the datasource
Fixed an issue that could cause the Tyk Gateway to panic when verifying signed customer plugin bundles
Fixed an issue where Tyk does not generate an analytics record when there is a proxying error (e.g. context cancelled event)
Fixed an issue where querying GraphQL API for __typename field would cause a 502
Changed
Tyk Gateway will now look first for a plugin built for the current version of Gateway and OS architecture before defaulting to the old-style naming convention; i.e. myplugin_{tyk-version}{os}{arch}.so will take precedence over myplugin.so.
Improved the behaviour with an MDCB deployment if there is a catastrophic event in the worker cluster and the worker Redis is reset. Previously it was necessary to change the groupidto ensure that the worker gateways would resynchronize with the controller; this patch alleviates this so that the worker will synchronise without a change to groupid. This requires MDCB v2.0.5.
Updated fasthttp dependency
Tyk Dashboard 4.3.2
Fixed
Fixed an issue in API Designer where API list could not be sorted
Prevented Dashboard to panic, when an update request was triggered to update a non existing Policy ID, by using a wrong ID.
Fixed Dashboard Analytics filtering, to panic the dashboard when more days were selected in the date range. This fixed addressed users that have configured Document DB as their storage choice.
Fixed Keys Update button on the Dashboard, to not be disabled when updating keys by key ID, even if the enable_update_key_by_hash configuration is set to false.
Dashboard is now persisting the HMAC secret, when updating the key data, even if a new policy has been added or the previous one was replaced.
API URLs in the Dashboard API Designer, present now the listen path as well, so that users can safely copy and use the API URL