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
When using consul and consul_kv as service discovery, it is hoped to support the incoming token to enable consul acl.
An example configuration file is as follows:
# for consul discovery: consul: servers: - "http://127.0.0.1:8500" - "http://127.0.0.1:8600" token: "consul-access-token" # add consul acl token config skip_services: - "service_a" #...
# for consul_kv discovery: consul_kv: servers: - "http://127.0.0.1:8500" - "http://127.0.0.1:8600" token: "consul-access-token" # add consul acl token config prefix: "upstreams" skip_keys: - "upstreams/unused_api/" #...
There is a discussion about consul acl in a similar issue #6692.
Official document of consul acl. And lua-resty-consul supports consul acl access control.
If the evaluation is feasible, please help to support it, thanks a lot~~
The text was updated successfully, but these errors were encountered:
Welcome to post a PR
Sorry, something went wrong.
feat: add token support for consul discovery(apache#9532)
52df2ed
add token support for consul_kv discovery(apache#9532)
50d80d7
fixed by #10278
No branches or pull requests
Description
When using consul and consul_kv as service discovery, it is hoped to support the incoming token to enable consul acl.
An example configuration file is as follows:
There is a discussion about consul acl in a similar issue #6692.
Official document of consul acl. And lua-resty-consul supports consul acl access control.
If the evaluation is feasible, please help to support it, thanks a lot~~
The text was updated successfully, but these errors were encountered: