> Here is an example: the default configuration of the `log-rotate` plugin.
you can add these configurations to plugin instead of local configuration file. IMO, These configurations should not be written in the configuration file, the current implementation is not good enough. junxu, and yuansheng, What problem does this metadta solve? I still don't understand. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing YuanSheng Wang <[email protected]> 于2020年9月14日周一 下午12:29写道： > Hi, > > I have another case, it seems that related to chen's case. > > For some plugin objects, their default configuration implementations are > based on local configuration files > and cannot be dynamically updated through the Admin API. > > If the default configuration of the plugin can be saved in etcd, we can > easily support the dynamic update of > the default configuration. > > ----------------------- > Here is an example: the default configuration of the `log-rotate` plugin. > > If it is stored in etcd, the administrator can switch log rotation rules at > any time on the console. > > ```shell > curl http://127.0.0.1:9080/apisix/plugin/log-rotate -X PUT -d ' > { > "interval": 3000, > "max_kept": 168 > }' > ``` > > > On Mon, Sep 14, 2020 at 11:46 AM Ming Wen <[email protected]> wrote: > > > Do you mean to support to writing of these metadata in Apache APISIX? > > But the open source version of Apache APISIX does not support clusters. > > > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > > > > > > junxu chen <[email protected]> 于2020年9月14日周一 上午11:16写道： > > > > > In this example: > > > > > > ETCDs (clusters) for Each Apache APISIX cluster are independent of each > > > other. > > > The `super system` manages and monitors multi Apache APISIX clusters. > > > > > > `clusterid` is used to identify different clusters, > > > `communication revision` is the version number of communication for > each > > > cluster with the `super system` > > > > > > > > > On Mon, Sep 14, 2020 at 9:33 AM Ming Wen <[email protected]> wrote: > > > > > > > > `clusterid` and `communication revision` , used to distinguish > > > different > > > > APISIX clusters for supper system. > > > > Is this multiple APISIX clusters sharing one etcd? I don't think > Apache > > > > APISIX can support this feature now. > > > > > > > > Thanks, > > > > Ming Wen, Apache APISIX & Apache SkyWalking > > > > Twitter: _WenMing > > > > > > > > > > > > wei jin <[email protected]> 于2020年9月14日周一 上午9:11写道： > > > > > > > > > I think it is useful > > > > > > > > > > junxu chen <[email protected]> 于2020年9月13日周日 下午1:34写道： > > > > > > > > > > > no, just store metadata in ETCD. > > > > > > > > > > > > On Sun, Sep 13, 2020 at 8:18 AM Zhiyuan Ju <[email protected] > > > > > > wrote: > > > > > > > > > > > > > Do you mean using some RDB in Cloud? > > > > > > > > > > > > > > Best Regards! > > > > > > > @ Zhiyuan Ju <https://www.shaoyaoju.org/> > > > > > > > > > > > > > > > > > > > > > junxu chen <[email protected]> 于2020年9月12日周六 下午10:38写道： > > > > > > > > > > > > > > > hello, community, > > > > > > > > > > > > > > > > Sometimes we need to dynamically store some metadata, and > don't > > > > want > > > > > to > > > > > > > add > > > > > > > > other dependencies such as database, but currently APISIX > does > > > not > > > > > > > support. > > > > > > > > > > > > > > > > A classic example: > > > > > > > > `clusterid` and `communication revision` , used to > distinguish > > > > > > different > > > > > > > > APISIX clusters for supper system. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > *MembPhis* > My GitHub: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix >
