In some use cases, you might want to create a number of plugins associated with
different entities in Kong but with the same configuration. In such a case,
if you change anything in the configuration of the plugin, you will have to
repeat it for each instance of the plugin.
In other use cases, the plugin configuration could be decided by a different
team, while the main Kong Gateway
configuration is directly used by an API owner.
Now, you can edit plugin configuration in a single place and you can see its
effect across multiple entities. Under the hood, decK takes the change and
applies it to each entity which references the plugin configuration that has
been changed. As always, use deck diff to inspect the changes before you
apply those to your Kong clusters.
Overriding fields in plugin configs
Settings configured in _plugin_configs are applied to all plugins with the same tag.
While those settings provide the baseline configuration, you can change specific
fields as needed for the entities that consume them.
Specific values set for entities take precedence over values defined in _plugin_configs.
For example, say that consumer fub in the previous example is still in the
gold-tier-limit, but needs a rate limit of 50 minutes instead of 20.
You can change this value just for that specific consumer: