-
Notifications
You must be signed in to change notification settings - Fork 254
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
🐛 Entity-feedback: Entity Feedback Plugin: GET /ratings/:entityRef returns 404 in production, but /ratings?ownerRef works #1523
Comments
Hmm going to need a bit more info to try to debug this - do you see any log messages in the backend that corresponds to that 404 request? can you also provide what Backstage and plugin versions you're on? |
Hello @kuangp, We are currently using Backstage version 1.22.19. Here are all the logs I see when I try to interact with the plugin:
Let me know it you need to more info |
Sorry forgot the plugins versions: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi @bchemsed1, is this still an issue? |
Plugin Name
Entity-feedback
📜 Description
The Entity Feedback plugin is experiencing inconsistent behavior in our production environment (EKS cluster behind a proxy). GET requests using query parameters work as expected, but requests using path parameters for entity references return a 404 error.
👍 Expected behavior
Both requests should return 200 OK with the appropriate data.
👎 Actual Behavior with Screenshots
The request with the entity reference in the path returns a 404 Not Found, while the request with the ownerRef query parameter works correctly.
👟 Reproduction steps
/api/entity-feedback/ratings?ownerRef=group:default/core
/api/entity-feedback/ratings/component:default/buildon-sandbox
📃 Provide the context for the Bug.
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: