guilhermevillote opened a new issue, #12393: URL: https://github.com/apache/apisix/issues/12393
### Current Behavior When a consumer is authenticated using a credential (e.g., via the key-auth plugin), any subsequent changes to that consumer's plugins or labels do not seem to take effect. It appears that the consumer's previous state is cached or persisted somewhere, and the updated configuration is not applied. ### Expected Behavior Any changes made to the consumer’s plugins or labels should take effect immediately, even when the request is authenticated via a previously created credential. ### Error Logs _No response_ ### Steps to Reproduce 1. Create a consumer with zero or more plugins (e.g., limit-count, fault-injection) and/or labels. 2. Create a credential for the consumer. 3. Make authenticated requests using the credential — the plugins and labels work as expected. 4. Modify the consumer: add/remove plugins or update labels. 5. Make the same request again using the same credential. 6. The request still behaves according to the old configuration — plugins/labels are not updated. ### Environment - APISIX version (run `apisix version`): 3.12 e 3.13 - Operating system (run `uname -a`): - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
