Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom kong plugins are not displayed in kong manager with the list of plugins #12740

Closed
1 task done
medbayoudh opened this issue Mar 16, 2024 · 3 comments
Closed
1 task done

Comments

@medbayoudh
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Kong version ($ kong version)

3.6.1

Current Behavior

we have a bunch of custom plugin for our kong gateway. We were using 3.4.2 and we were able to see those custom plugins in the list of plugins in kong-manager. Now after upgrading to 3.6.1 we are not able to see them. Configuring routes with custom plugins using the REST API is working fine and the plugins are recognized but unfortunately we are not able to configure them directly from kong-manager (which is a way easier)

Expected Behavior

  • Custom plugins are displayed in the list of plugins
  • Configuring custom plugins for routes or services using kong-manager

Steps To Reproduce

  1. install custom plugin P
  2. create route A
  3. configure custom plugin P for route A using kong-manager
  4. custom-plugin does not appear in the list of configurable plugins

Anything else?

No response

@Maurici093
Copy link

I have exactly the same behavior today :'(

@sumimakito
Copy link
Member

Hello @medbayoudh - Thank you for reporting this. We are currently looking into this issue.

This issue should only affect the plugin select page. Meanwhile, you may access the URL for the plugin configuration page directly as a workaround.

For example:

http://localhost:8080/default/plugins/select/<YOUR_CUSTOM_PLUGIN_NAME>

@sumimakito
Copy link
Member

Hi @medbayoudh - I just confirmed with the team that this issue has been fixed in the latest as well as the 3.6.x branch. This fix will be delivered in the next major or minor release. I will close this issue for now. You can reply or reopen it if you have any other needs.

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

No branches or pull requests

4 participants