Hi community,

As we all know, one of the pros of Apache APISIX is dynamic, users
don't have to reload Apache APISIX if they want to operate Route,
Upstream, or other core resources. That's excellent. However, there
are still some features provided by Apache APISIX are static, for
instance:

1. Some plugins (le.g., og_rotate, skywalking plugins) have the
`plugin_attrs` settings.
2. Enabled plugin list
3. Service discovery.
4. ...

This proposal is not for discussing how to make the above features
dynamic but aims at if we should move towards such a direction and no
longer rely on the static config.yaml and make APISIX more dynamic.
The dependency of config.yaml makes the Apache APISIX dashboard or
other control plane implementations powerless, as users still have to
modify the config.yaml of each Apache APISIX instance, which is
tedious and cumbersome.

What's your idea?

Best regards
Chao Zhang

https://github.com/tokers

Reply via email to