When your applications run across multiple environments (development, staging, and production) or multiple regions, you need to keep their Nacos configurations consistent. Microservices Engine (MSE) provides two synchronization methods based on whether the source and destination namespaces are in the same region:
| Scenario | Method | How it works |
|---|---|---|
| Namespaces in the same region | Clone | Copies configurations between namespaces within the MSE console. No file download required. |
| Namespaces in different regions | Export and import | Exports configurations to a .zip file, which you then import into the destination region. |
Prerequisites
Before you begin, make sure that you have:
An MSE Nacos instance in each region where you want to synchronize configurations
At least one configuration in the source namespace
Clone configurations within the same region
Use the clone function to copy configurations between namespaces in the same region without downloading any files.
Log on to the MSE console and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Instances.
On the Instances page, click the name of the instance.
In the left-side navigation pane, choose Configuration Management > Configurations.
(Optional) Select a namespace to filter configurations. You can also filter by Group, Data ID, Application, or Tag.
Select the configurations to synchronize and click Clone in the lower-left part of the page.
In the Clone Configuration dialog box, select the target namespace from the Destination Namespace drop-down list and click Start Clone.
If configurations with the same Data ID and Group already exist in the destination namespace, the Configuration Conflicts dialog box appears. Select the configurations to overwrite and click OK, then click Start Clone. To compare configurations between the Source Namespace and Destination Namespace before overwriting, click View Diff in the Actions column. The Configuration Content Comparison dialog box displays a side-by-side diff.
After cloning, open the destination namespace and verify that the configurations were synchronized correctly.
Export and import configurations across regions
When the source and destination namespaces are in different regions, export configurations to a .zip file from the source region, then import the file into the destination region.
Export configurations
Log on to the MSE console and select the source region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Instances.
On the Instances page, click the name of the instance.
In the left-side navigation pane, choose Configuration Management > Configurations.
(Optional) Select a namespace to filter configurations. You can also filter by Group, Data ID, Application, or Tag.
Select the configurations to export and click Export in the lower part of the page.
In the Export Configuration dialog box, verify the selection and click Start Export. The configurations are downloaded as a .zip file to your local machine.
Import configurations
In the MSE console, switch to the destination region in the top navigation bar and open the target instance.
In the left-side navigation pane, choose Configuration Management > Configurations.
Select the target namespace from the Namespace drop-down list, then click Import Configuration.
In the Import Configuration dialog box, set the following parameters:
Parameter Description Destination Namespace The namespace to import configurations into. Defaults to the namespace selected on the Configurations page. Same Configurations How to handle configurations with the same Data ID and Group in the destination namespace. Options: Stop Import -- cancels the import and no configurations are synchronized. Skip -- skips duplicate configurations and imports the rest. Overwrite -- replaces duplicate configurations with the imported versions. Configuration File Click Upload File and select the exported .zip file. Click OK to start the import.
Do not modify the .zip file before importing. Editing the exported file may cause the import to fail. To change configurations, import them first, then edit them in the destination namespace.
After importing, open the destination namespace and verify that the configurations were synchronized correctly.
Open-source Nacos compatibility
MSE supports importing configuration packages exported from both older and newer versions of the open-source Nacos console. Configuration packages exported from MSE are also compatible with the open-source Nacos console (newer version).