Skip to content
New issue

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

Confirmation of no_consumer plugin flags #2235

Closed
pauldaustin opened this issue Mar 22, 2017 · 2 comments · Fixed by #2237
Closed

Confirmation of no_consumer plugin flags #2235

pauldaustin opened this issue Mar 22, 2017 · 2 comments · Fixed by #2237

Comments

@pauldaustin
Copy link

Summary

I think there might be some additional plugins that wouldn't be for consumers (e.g. ldap-auth, logging plugins). Can you add no_consumer=true to those that aren't meant to be included for consumers.

It might also be nice to expose the no_consumer flag in the /plugins/schema/{pluginName} response.

The following table shows those plugins that have no_consumer=true.

Plugin Name No Consumer
acl true
aws-lambda
basic-auth true
bot-detection true
correlation-id
cors true
datadog
file-log
galileo
hmac-auth true
http-log
ip-restriction
jwt true
key-auth true
ldap-auth
log-serializers
loggly
oauth2 true
rate-limiting
request-size-limiting
request-transformer
response-ratelimiting
response-transformer
runscope
statsd
syslog
tcp-log
udp-log
@Tieske
Copy link
Member

Tieske commented Mar 22, 2017

thx for checking that.

Though I don't see why the logging plugins should be 'no-consumer' ?

@pauldaustin
Copy link
Author

You're right I can see cases for per consumer logging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants