Description
Where is the problem?
https://docs.konghq.com/gateway/latest/key-concepts/plugins/
What happened?
I started experimenting with kong and got stuck because different Request Transformer configurations on a route and the service the route targeted were not applied as I expected.
In the end it boils down for me not having understood what https://docs.konghq.com/gateway/latest/key-concepts/plugins/#precedence actually means when it says "plugin instance".
Especially "plugin instance" isn't explained before hand on the page.
When looking at the Kong UI and Rest API there are only "Plugins" being mentioned. So I was thinking that I do create a plugin instance if I click on "+ New Plugin" in the UI or http POST to the corresponding endpoint, which isn't the case. It just creates a plugin configuration (or whatever the exact terminology is) which is then picked up according to the precedence rules by the plugin.
Exact details on my experimentation with kong can be found on https://stackoverflow.com/questions/79025767/how-to-use-different-request-transformer-instances-on-service-and-route-at-the-s
What did you expect to happen?
I expect the documentation to use a consistent terminology with regard to the UI and Kong Configuration Rest API that is explained unambigously. Especially the documentation must explain the term "Plugin instance" and how that compares to the term "Plugin" used in the UI and how these are applied to a request/response being processed clearly so that a reader does not make the false assumption that execution the "+ New Plugin" action doesn't create a plugin instance which is executed without dependencies on how other entities (routes, services, global plugins) are being configured.
Code of Conduct and Community Expectations
- I agree to follow this project's Code of Conduct
- I agree to abide by the Community Expectations