You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/11/09 03:06:30 UTC
[GitHub] [apisix] lilihongjava opened a new issue #2664: request help: Suggestions for storing dynamic rules in apifix
lilihongjava opened a new issue #2664:
URL: https://github.com/apache/apisix/issues/2664
### Issue description
Requirement: a request has an application ID and a developer ID. it is necessary to find out the private key(there is a management console that can be configured) corresponding to the application and developer in a place to encrypt the request content. This data(private key) is dynamic and will change frequently. Now i need to select a key value library. At present, we plan to put redis or etcd. For redis, it is a memory database, and it is also used for limit-req. The reason why etcd is put is that apifix comes with it. I understand that etcd has a watch mechanism, but I don't know whether apifix provides a function to get the latest data stored in etcd？ And whether in the apisix plugin can get the latest data in real time in memory？
Or do you have any better suggestions for dynamic data storage? Thank you
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] lilihongjava commented on issue #2664: request help: Suggestions for storing dynamic rules in apifix
Posted by GitBox <gi...@apache.org>.
lilihongjava commented on issue #2664:
URL: https://github.com/apache/apisix/issues/2664#issuecomment-723732119
Thank you for your prompt reply
Is there any reference example？
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] spacewander commented on issue #2664: request help: Suggestions for storing dynamic rules in apifix
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #2664:
URL: https://github.com/apache/apisix/issues/2664#issuecomment-723733985
How we use the `config_etcd` is the best example, which is workable and battle-tested.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] lilihongjava closed issue #2664: request help: Suggestions for storing dynamic rules in apifix
Posted by GitBox <gi...@apache.org>.
lilihongjava closed issue #2664:
URL: https://github.com/apache/apisix/issues/2664
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] spacewander commented on issue #2664: request help: Suggestions for storing dynamic rules in apifix
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #2664:
URL: https://github.com/apache/apisix/issues/2664#issuecomment-723728740
For how we get the latest data in etcd, you can take a look at https://github.com/apache/apisix/blob/master/apisix/core/config_etcd.lua.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org