Open gregoirechauvet opened 1 year ago
@gregoirechauvet Thank you very much for this ticket, and your investigation! I have been able to reproduce the issue with your steps. There are indeed 2 different issues:
we are going to provide fixes as soon as possible and keep you on touch.
About the different endpoints for consumer groups, this is expected. There are some differences in the implementation between Konnect (saas) vs Kong. Usually, konnect users don't deal with the endpoint directly so that's why it is not documented.
Hi @gregoirechauvet , would you mind testing it again with decK v1.25.0
? This version should have fixed this issue.
Tags have been added to consumer groups in https://github.com/Kong/deck/pull/823 But despite this addition, it seems a distributed configuration doesn't work with consumer groups. I've tested it on deck v1.17.2 which is the version that includes the consumer group tags addition.
Reproduction
Create consumer groups from a configuration with
select_tags: global
.And then try to create a service from another location with another select tag:
It results in the following output. The consumer groups should be deleted from decK's perspective. Whereas other entities such as services and plugins are ignored properly.
Investigation
I've investigated decK hoping I could contribute to it by fixing this behavior. But my conclusion is that the error comes from the
/v1/consumer-groups
endpoint that doesn't filter ontags
: https://github.com/Kong/deck/blob/629712b81ebebf9df4b2b60127cc62e9a4b8cb52/konnect/consumer_group.go#L432The full endpoint decK is using in my case is:
I've tried it on the CLI, and it ignores the
tags
when sent as parameters (?tags=client-api
). As opposed to endpoints such as/services
which filter correctly on tags. I could not find any documentation about/v1/consumer-groups
, only about/consumer_groups
. Any reason not to use the second one instead? Should the first one be documented?