Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

When changing kong nodes / adding new onces consumers are not listed #23

Closed
bakstad opened this issue Feb 23, 2017 · 7 comments
Closed

Comments

@bakstad
Copy link

bakstad commented Feb 23, 2017

All consumers are listed after first addition of kong nodes, but when I add another one or change between multiple nearly every consumer is missing.

@pantsel
Copy link
Owner

pantsel commented Feb 23, 2017

If all Kong nodes are viewing the same db, you will need to sync the consumers for each node from Konga.
Konga queries the consumers from it's own db where they're saved in relation to the node they where created.

This will change in the future but for now this is how things work.

If each Kong node is a separate instance with its own db, then another node's consumers are not supposed to be shown.

@bakstad
Copy link
Author

bakstad commented Feb 23, 2017

Oh ok. That I don't want. I want Kong to be the owner of the consumers.

So if I sync I will loose my consumers because I have none in Konga except the default ones?

@pantsel
Copy link
Owner

pantsel commented Feb 23, 2017

Syncing only affects consumers on Kongas db. You will not loose any consumers in Kongs db.

Kong's consumers that don't exists in Konga's database will be imported
while Konga's consumers that don't exist in Kong's database will be removed (from Konga's db)

@bakstad
Copy link
Author

bakstad commented Feb 23, 2017

Hm ok. Syncing did not help. In the log from Konga i see all my consumers, but only a few shows up in the GUI.

@pantsel
Copy link
Owner

pantsel commented Feb 23, 2017

Can you maybe post a screenshot of the GUI and logs so i can understand what's going on? It seems to be working on my end.

@pantsel
Copy link
Owner

pantsel commented Mar 12, 2017

Hi @bakstad ,
check out the new release and please report back if this issue has been fixed so we can close it.
Thnx.

@bakstad
Copy link
Author

bakstad commented Mar 13, 2017

Hi,

Great job on the 0.5.x! This seems to be fixed now, Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants