We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
admin api will pollute and save plugin_conf into etcd when calling plugin's function check_schema. e.g. https://github.com/apache/incubator-apisix/blob/master/apisix/plugins/proxy-rewrite.lua#L111
apisix version
the runtime data of the plugin has be saved into etcd.
the runtime data of the plugin should't be saved into etcd.
The text was updated successfully, but these errors were encountered:
only Admin API has this bug.
Admin API
Sorry, something went wrong.
I think we should remove apisix.admin.plugins.check_schema, just check schema in sync_data
@wrl96 Your way is dangerous, we don't allow dirty data to be stored in etcd.
I will fix this bug
etcd
bugfix: should not save the runtime data of plugin into etcd. (#1910)
2d667ec
Fixed #1836 .
membphis
nic-chen
Successfully merging a pull request may close this issue.
Issue description
admin api will pollute and save plugin_conf into etcd when calling plugin's function check_schema.
e.g. https://github.com/apache/incubator-apisix/blob/master/apisix/plugins/proxy-rewrite.lua#L111
Environment
apisix version
): 1.4Minimal test code / Steps to reproduce the issue
What's the actual result? (including assertion message & call stack if applicable)
the runtime data of the plugin has be saved into etcd.
What's the expected result?
the runtime data of the plugin should't be saved into etcd.
The text was updated successfully, but these errors were encountered: