feat: add support to consumer_groups

[GGabriele]

https://docs.konghq.com/gateway/3.0.x/admin-api/consumer-groups/reference/

Needs some go-kong changes first: Kong/go-kong#221

[codecov-commenter]

Codecov Report

Base: 38.88% // Head: 35.52% // Decreases project coverage by -3.35% ⚠️

Coverage data is based on head (0f9a7a9) compared to base (be0eaa0).
Patch coverage: 2.43% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #760      +/-   ##
==========================================
- Coverage   38.88%   35.52%   -3.36%     
==========================================
  Files          88       92       +4     
  Lines       10205    11219    +1014     
==========================================
+ Hits         3968     3986      +18     
- Misses       5851     6836     +985     
- Partials      386      397      +11     

Impacted Files	Coverage Δ
cmd/common.go	5.20% <0.00%> (-0.04%)	⬇️
cmd/common_konnect.go	7.22% <0.00%> (-0.17%)	⬇️
cmd/reset.go	0.00% <0.00%> (ø)
diff/diff.go	0.00% <0.00%> (ø)
diff/order.go	79.16% <ø> (ø)
dump/dump.go	1.41% <0.00%> (-0.16%)	⬇️
file/types.go	59.71% <0.00%> (-1.42%)	⬇️
konnect/consumer_group.go	0.00% <0.00%> (ø)
state/builder.go	0.00% <0.00%> (ø)
state/consumer_group.go	0.00% <0.00%> (ø)
... and 11 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[aboudreault]

Great job @GGabriele !! I looked at all files and I don't see any blocker. There is a lot in this PR and it's not obvious to catch possible bugs while reviewing. However, I tested this deck PR with Konnect with multiple different cases (sync/dump/diff etc.) and things seem to work well. I am continuing some more testing but I'd say +1.

[sscarpanti70]

Hello @GGabriele , about consumer-groups support, with 1.17.0 deck release I cannot dump or sync from free kong anymore, while with 1.16.0 was possible. The error given was: Error: reading configuration from Kong: consumer_groups: HTTP status 403 (message: "Enterprise license missing or expired")

[GGabriele]

Hi @sscarpanti70 , what Kong version are you using?

[sscarpanti70]

3.1.1.1, without any license so far Il giorno gio 12 gen 2023 alle ore 16:02 Gabriele ***@***.***> ha scritto:

…

Hi @sscarpanti70 <https://github.com/sscarpanti70> , what Kong version are you using? — Reply to this email directly, view it on GitHub <#760 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5G6A4MSZAHH25DDDGH6KIDWSAMI3ANCNFSM6AAAAAAQ4KCVZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sscarpanti70]

I can't understand if since 1.17.0 deck a license is needed to sync with kong or I have to add a specific user to fix connection Il giorno gio 12 gen 2023 alle ore 16:08 Stefano Scarpanti < ***@***.***> ha scritto:

…

3.1.1.1, without any license so far Il giorno gio 12 gen 2023 alle ore 16:02 Gabriele < ***@***.***> ha scritto: > Hi @sscarpanti70 <https://github.com/sscarpanti70> , what Kong version > are you using? > > — > Reply to this email directly, view it on GitHub > <#760 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/A5G6A4MSZAHH25DDDGH6KIDWSAMI3ANCNFSM6AAAAAAQ4KCVZM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[GGabriele]

I see the problem, you're using an enterprise version of Kong without a license and decK is not checking for this case.

I will push a fix and do path release. Thanks for raising this!

[sscarpanti70]

Hello Gabriele, I just let you know about a workaround we found with 1.17.1, simply specifying workspace deck -w default sync -s setup_3x.yaml --select-tag inso-single It works perfectly. Also dump. Il giorno gio 12 gen 2023 alle ore 21:29 Gabriele ***@***.***> ha scritto:

…

I see the problem, you're using an enterprise version of Kong without a license and decK is not checking for this case. I will push a fix and do path release. Thanks for raising this! — Reply to this email directly, view it on GitHub <#760 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5G6A4K4VAYWS5M7SZWOOGTWSBSUNANCNFSM6AAAAAAQ4KCVZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[GGabriele]

Thanks for letting me know!

In the mean time, I just opened this: #821

[sscarpanti70]

That's great! Il giorno ven 13 gen 2023 alle ore 14:58 Gabriele ***@***.***> ha scritto:

…

Thanks for letting me know! In the mean time, I just opened this: #821 <#821> — Reply to this email directly, view it on GitHub <#760 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5G6A4PBA75OER4CO4S5N6TWSFNRXANCNFSM6AAAAAAQ4KCVZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>