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
In Kong 2.8 and 3.4, Kong allows users to create consumer group policies (ad. rate limiting) in Kong Manager. However, deck dump generates a configuration that does not match the policy config in Kong Manager. This causes several problems.
Firstly, when running a deck sync with the generated config, deck creates a news global adv. rate limiting plugin that is now associated with the consumer group instead of updating or creating a policy in the consumer group. Secondly, the newly created global adv. rate limiting plugin only contains the limit and window size. There is no associated Redis configuration (which is lost).
Therefore, deck dump and deck sync for consumer group policies do not honour what is configured in Kong.
The text was updated successfully, but these errors were encountered:
Created from slack thread:
In Kong 2.8 and 3.4, Kong allows users to create consumer group policies (ad. rate limiting) in Kong Manager. However, deck dump generates a configuration that does not match the policy config in Kong Manager. This causes several problems.
Firstly, when running a deck sync with the generated config, deck creates a news global adv. rate limiting plugin that is now associated with the consumer group instead of updating or creating a policy in the consumer group. Secondly, the newly created global adv. rate limiting plugin only contains the limit and window size. There is no associated Redis configuration (which is lost).
Therefore, deck dump and deck sync for consumer group policies do not honour what is configured in Kong.
The text was updated successfully, but these errors were encountered: