You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am developing new filter using Easegress,in other api gateway sometime I need to use cluster cache like redis to cache expired token,but in Easegress it already has etcd embedded and I don't want to introduce new outer cache component, so is it possible to use Easegress own cluster storage api do something like this, or is it a proper way?
The text was updated successfully, but these errors were encountered:
Please check if the CustomData feature meets your requirement (the PR has been merged, but the feature has not been released yet, please get the latest code from the main branch).
Or, you can use the APIs in the cluster package directly for data storage.
Thanks, CustomData cannot support expired data store. I investigate the source code,currently the only way to to initialize cluster storage api for client user is to get command opt params and call cluster.New(opt) like the way in cmd/server/main.go. We should support something like factory pattern in pkg/cluster/cluster_interface.go so client user can get cluster instance conveniently.
@jthann You don't have to initialize new cluster instance, because Easegress creates one instance at startup and it's reused everywhere. Here's example how you access to the global cluster instance from Filter.Init function.
I am developing new filter using Easegress,in other api gateway sometime I need to use cluster cache like redis to cache expired token,but in Easegress it already has etcd embedded and I don't want to introduce new outer cache component, so is it possible to use Easegress own cluster storage api do something like this, or is it a proper way?
The text was updated successfully, but these errors were encountered: