MarcCain-Scott commented on issue #2404: URL: https://github.com/apache/apisix-ingress-controller/issues/2404#issuecomment-3242522577
Wow, thank you so much. I will admit that most of this plugin was created by an AI because no one here knows anything about Lua, myself included. I found the documentation to be difficult to find examples that worked with the current versions and there are many contradictions. We had discussed using a plugin runner to do this, but since this is the only custom plugin used and it is only used for 11 total routes, we decided not to complicate things and use the serverless plugin. I didn't realize it would have such access to the Apisix process and I will put it on the list to replace it. We will continue to use Apisix, this was our only operational issue with it. Everything else about how it performs and integrates into our environment has been great. The obly issue I have is that the documentation can be lacking, so we have relied on AIs more to parse and give examples. Clearly that has caused us some problems. FYI this function just returns when there is no valid JWT because later on in the chain an invalid JWT will cause the call to be rejected. So there was no need to add extra logic here. This plugin was just to bridge a gap to replace older functionality of the older solution which we were replacing with Apisix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
