Skip to content

Config Change Plugin

Translated by AI.

Community has long been hoping for Nacos Configuration Center to provide notifications to specific systems when configurations change. These notifications are used for recording, warning, and auditing purposes. Before version 2.3.0, the only way to achieve this was by simulating Nacos client subscription to the configurations. This approach involved subscribing to changes in core configurations and executing functionalities such as sending records and warnings upon receiving change notifications.

However, this implementation had a few significant issues. Firstly, individual configurations needed to be added one by one, making it difficult to capture all configuration changes. Secondly, functionalities could only be executed after configuration changes, and there was no capability for performing pre-change operations such as format validation or whitelist validation.

To address these limitations, starting from Nacos version 2.3.0, Nacos introduced support for injecting configuration change plugins through the SPI. This allows users to define custom plugins to execute specific logic before and after configuration changes. Examples of such logic include format validation, whitelist validation, and webhook integrations.

These enhancements provide more flexibility and control for users to implement their own custom logic before and after configuration changes in Nacos Configuration Center.

Concepts in Config Change Plugin

Nacos’s configuration change plugin design takes inspiration from the aspect-oriented programming (AOP) paradigm. It treats configuration change operations, such as adding, updating, and deleting, as the pointcuts and weaves the plugins before and after these pointcuts.


Nacos has categorized the configuration change operations based on their behaviors and sources. These configuration change operations are defined as several ConfigChangePointCutTypes in The specific details are as follows:

PointCut NameDescriptionStart version
PUBLISH_BY_HTTPConfiguration is published through the HTTP interface, including creating and modifying configurations.2.3.0
PUBLISH_BY_RPCConfiguration is published through the gRPC interface, including creating and modifying configurations.2.3.0
REMOVE_BY_HTTPConfiguration is removed through the HTTP interface.2.3.0
REMOVE_BY_RPCConfiguration is removed through the gRPC interface.2.3.0
IMPORT_BY_HTTPConfiguration is imported through the HTTP interface.2.3.0
REMOVE_BATCH_HTTPConfigurations are batch removed through the HTTP interface.2.3.0


In Nacos, the configuration change plugins need to be executed before or after the ConfigChangePointCutTypes by selecting the ConfigChangeExecuteTypes. These execution types are defined in The specific details are as follows:

Execute TypeDescriptionStart version
EXECUTE_BEFORE_TYPEPlugin execute Before ConfigChangePointCutTypes2.3.0
EXECUTE_AFTER_TYPEPlugin execute After ConfigChangePointCutTypes2.3.0

Plugin Development

To develop a config change plugin for the Nacos server, you first need to depend on the relevant API of the config change plugin.


${project.version} is the Nacos version, at least 2.3.0.

Then implement interface, which include following method:

Method nameParametersReturnDescription
getServiceTypevoidStringReturns the name of the plugin, which is used to differentiate between different types of plugin implementations.
getOrdervoidintReturns the execution order of the plugin. The configuration change plugin is designed with a chain plugin pattern, where multiple plugins are executed in order. The smaller the return value of getOrder, the earlier the plugin is executed.
executeTypevoidConfigChangeExecuteTypesReturns ConfigChangeExecuteTypes implemented by the plugin.
pointcutMethodNamesvoidConfigChangePointCutTypes[]Returns ConfigChangePointCutTypes where the plugin is implemented.
executeConfigChangeRequest,ConfigChangeResponsevoidExecutes the actual logic of the plugin.

ConfigChangeRequest and ConfigChangeResponse refer to the contents passed in during the execution of logic and the resulting execution outcome, respectively.

ConfigChangeRequest mainly include follow contents:

Field nameTypeDescription
requestTypeConfigChangePointCutTypesThe pointcut types of this configuration change
requestArgsHashMap<String, Object>The actual parameters of this configuration change, mainly including namespace, group, dataId, content, etc., with different parameters for different pointcut types

ConfigChangeResponse mainly include follow contents:

Field nameTypeDescription
responseTypeConfigChangePointCutTypesThe pointcut types of this configuration change
isSuccessbooleanIndicates whether the execution is successful. When the return value is false, the configuration change will be intercepted and the failure result will be returned directly
retValObjectReturn content, a reserved field that is currently not used
msgStringExecution result information, obtained when isSuccess is false, used to return information to the client
argsObject[]The execution parameters of the configuration change, effective for the EXECUTE_BEFORE_TYPE plugin type. It can be used to modify the content of the actual executed configuration change, such as changing certain values in content to other values

Load Plugin

After the plugin finished, it needs to be packaged into jar/zip and places in the classpath of the nacos server. If you don’t know how to add plugins into the classpath, please place plugins under ${nacos-server.path}/plugins directly.

After Adding plugins into classpath, also need to modify some configuration in ${nacos-server.path}/conf/

### The name of the config change plugin enabled in Nacos, corresponding to the return value of's getServiceType method.

After restarting the Nacos cluster and completing the startup, you can see the following logs in ${nacos-server.path}/logs/plugin-control.log:

[ConfigChangePluginManager] Load ${className}(${classFullName}) ConfigChangeServiceName(${configChangePluginName}) successfully.

Custom Plugin properties

Some plugins may want to set certain parameters through a configuration file. Custom plugins can modify the following configurations in ${nacos-server.path}/conf/ to achieve this:

### The name of the config change plugin enabled in Nacos, corresponding to the return value of's getServiceType method.

In ConfigChangeRequest, getting properties by following way:

final Properties properties = (Properties) configChangeRequest.getArg(ConfigChangeConstants.PLUGIN_PROPERTIES);
final String ${propertyKey} = properties.getProperty("${propertyKey}");

Plugin Demo

In the nacos-group/nacos-plugin repository, there is a demo implementation of a configuration change plugin. This demo plugin implements validation of the configuration content format, validation of the whitelist for importing configuration names, and a webhook callback after the change. To use this plugin, you need to package it as a JAR/ZIP file and place it in the classpath of the Nacos server. Additionally, add the following configuration in ${nacos-server.path}/conf/

# webhook
# It is recommended to use EB
# The content push max capacity ,byte
# whitelist
# The import file suffixs
# fileformatcheck,which validate the import file of type and content