You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently some plugins, like the SSL Plugin, don't support a customer_id because of technical limitations or because it wouldn't make sense.
Currently we discourage using consumer_id just by not documenting it, but we should have a way to block setting a consumer_id in the API itself returning a message like: "The consumer_id cannot be specified for this plugin".
Should the consumer_id be part of each plugin's schema maybe?
The text was updated successfully, but these errors were encountered:
Handled with a custom check in SSL's `on_insert` event. Waiting for
global plugins implementation for a cleaner, more generic solution.
FixKong#322
Former-commit-id: cfb6a0b1632e4f412bf168ffd60b52d4d58e80c1
Currently some plugins, like the SSL Plugin, don't support a
customer_id
because of technical limitations or because it wouldn't make sense.Currently we discourage using
consumer_id
just by not documenting it, but we should have a way to block setting aconsumer_id
in the API itself returning a message like: "The consumer_id cannot be specified for this plugin".Should the
consumer_id
be part of each plugin'sschema
maybe?The text was updated successfully, but these errors were encountered: