LetsGO
LetsGO
looks not a dashboard bug, the data is fetched from etcd in real time. If you want, we can communicate by voice
> This seems to be as expected, there is a caching layer between Dashboard and etcd. you are right, we have a layer of cache
According to etcd doc, `Disaster recovery` requires a restart of etcd, which means that all previous client links will be invalidated, and the old data you see is just the...
you are right, but we can set dialOption to control the behavior of reconnection ref: https://pkg.go.dev/go.etcd.io/etcd/client/v3#Config, https://pkg.go.dev/google.golang.org/[email protected]/backoff
Currently, there is no re-watch after watch fails, do you have any good ideas?
can assign it to me?
1. I hope V3 can support managing multiple `apisix` nodes 2. Login add MFA checking
> I don't think this change will help improve the user experience, let's hear more people's opinions. Agree +1, BTW according to APISIX [docs](https://apisix.apache.org/docs/apisix/architecture-design/service/), Service is an abstraction of route,...
How about `google authenticator`? as far as I know, it is more popular. The 2FA of `jumpserver` is implemented with it
Hi, @matkocsis The plugins on `Consumer` and `Route` are merged by priority (`Consumer` > `Route`), according to the description you provided, `limit-count` is disabled on `Consumer` but `limit-count` on `Route`...