Publish your extension in multiple Data Centre

In Sigma, you can develop an extension for all data centres in a single place. If the extension code is compatible for all DCs, you can sync the extension to all DCs in a single click.

While you publish an extension, you'll be prompted to choose the publishing details of the extension (as in the screenshot below). If you choose Yes to enable Multi-DC, the extension will be published across the following data centres: US, IN, AU, EU, CN, JP, CA, and SA. This action is irreversible. This Multi-DC sync feature is available for both Public and Private extensions.

For instance, when you create an extension for IN DC and want the extension to be available in other DCs as well, you can enable this Multi-DC option.

If Multi-DC sync is only enabled in the third version of the extension, the first and second versions of the extension won't be available for installation in other DCs. All upcoming versions, however, will be automatically synced across the DCs.

You can verify if Multi-DC is enabled by navigating to General Details of the extension.

When Multi-DC is enabled, the status of the sync will be listed along with the version on clicking the Multi-DC icon.

When Multi-DC is enabled, the extension will be deployed in all DCs. In case, there is a failure in one of the DCs, you can synchronize deployment for the specific DC alone by clicking Re-Initialize Sync.

Currently, we support US, IN, AU, EU, CN, JP, CA, and SA data centers. When support for a new DC is introduced, you can enable it for your existing extensions as well by clicking Initialize Sync.

Install URL

For Private extensions, Install URL for each DC can be generated when you choose the respective DC from the drop-down. This URL can be shared with users to install the extension in the respective DCs. On the other hand, Public extensions will be listed in the respective Marketplace for the users to install.

Multi-DC sync feature is currently available only for Zoho Desk extensions. To setup Multi-DC for Zoho Desk extension, you can refer to this help document.

Multi-DC Sync for Extensions using Custom Connections

Early Access
This feature is not enabled for all users. If you’d like to try it out, please email our support team for early access.

This feature is supported only for Zoho Projects service extensions.
Once access is enabled, you can follow the steps outlined in this guide.

To support Multi-DC sync for extensions with custom connections, the dcConnectors key is introduced in the plugin-manifest.json. This configuration ensures that extensions created in the Primary Data Center (DC) are synced to the DCs specified in dcConnectors while publishing extension with connections.

How to Configure

1. Create Connections in the Primary DC

Create all the required custom connections in the Primary DC from the Connections page.
Refer to Sigma Connections documentation for detailed steps on creating connections.

2. Get the Connection Details

After publishing the connection, a connection JSON will be available under the Sample Code section.
This JSON contains the required details (such as connection link name) needed for configuration.

3. Update the Plugin Manifest

Add the dcConnectors key to your plugin-manifest.json and store the connectionLinkName under the appropriate sharedBy for each DC in the below mentioned format.

Format:

{
  "dcConnectors":{
      "{DCType}":{
         "{sharedBy}":[
            "{connectionLinkName1}",
            "{connectionLinkName2}",
            "etc"
         ] 
      },
      "{DCtype}":{
        "{sharedBy}":[
          {
            "actualConnectionName":"aliasConnectionName"
          },
          "etc"
        ]
      }
  }
}

Sample plugin-manifest.json format for Dc connector

Alias Connection Name Mapping

An aliasConnectionName maps a DC-specific connection to a common connection link name used across all DCs.

When to use

Use alias mapping when separate custom connection requires in other DC's — for example, when different DCs have different authorization URLs.

Configuration Steps

Create the required custom connection for each DC using the DC-specific configurations (e.g., auth URL).
Assign a DC-specific connection name for each DC.
Map the DC-specific connection to a common alias in dcConnectors

{
  "dcConnectors":{
      "US":{
         "57294746":[
            "google_drive",
            "projects_conn"
         ]
      },
      "EU":{
         "57294746":[
          {
            "projects_eu_conn":"projects_conn"
          },
          "google_drive"
        ]
      }
  }
}

In this example:

projects_conn is the common alias
projects_eu_conn is the EU-specific connection
The extension continues to use projects_conn across all DCs

4. Add All Required DC Keys

Before publishing, manually add all required DC keys in the dcConnectors object.

Supported DC Keys

US, EU, AU, IN, JP, UAE, CN, CA, SA, UK

If a DC key is not included in the dcConnectors object:

A notification will be displayed during publishing
Skipped DCs will be listed
The extension will not be synced to those DCs.

Adding a New DC

When a new DC is introduced:

Add the new DC key under dcConnectors.
Provide the connection mappings in the same format.
Republish the extension.

Migrating from Existing Connectors to DC Connectors

In a DC Connector-enabled workspace: When an extension is run or published, existing entries under the connectors key are automatically converted into dcConnectors for the current DC
For Multi-DC Sync : Developers must manually add all required DC keys in dcConnectors before publishing to ensure proper synchronization

Publish your extension in multiple Data Centre | Online Help | Sigma | Multi DC Connectors