Dynamically migrate macro parameters

Available Confluence 5.8 and later

This guide describes how to use the new macro-schema-migrator plugin module to migrate parameters of a macro from one schema version to another.  For example, to migrate the parameters of a macro from individual parameters for label, space, author to a single CQL parameter.  

In this guide we'll be migrating a simplified Content by Label macro.


Here's the original macro module descriptor. Note the multiple parameter types:

    <macro name="contentbylabel" key="simplecontentbylabel"
            <parameter name="label" type="string" required="true">
            <parameter name="spaces" type="spacekey">

This is the new module descriptor with a single CQL parameter and schemaVersion: 

<macro name="contentbylabel" key="simplecontentbylabel" schema-version="2"
        <parameter name="cql" type="cql" required="true">

To migrate from the schema version the plugin should declare a new macro migration module in atlassian-plugin.xml, specifying the schema version that the macro migration migrates from:

<macro-schema-migrator key="contentbylabel-migrator" macro="simplecontentbylabel"

And implement the MacroMigration interface:

public class LabelledContentMacroCqlSchemaMigrator implements MacroMigration
	public MacroDefinition migrate(MacroDefinition macro, ConversionContext context)
        String cqlQuery = String.format("label in (%s) and space = %s", 
        macro.setParameter("cql", cqlQuery);
        macro.setTypedParameter("cql", cqlQuery);
        macro.setSchemaVersion(2);  // set the schema version to be the target schema version

When does macro migration occur?

Migration is performed by the MacroSchemaMigrator dynamically when marshalling from the MacroDefinition to the content body representation, specifically it occurs in the: 

  • StorageMacroV2Marshaller
  • ViewMacroMarshaller
  • DelegatingEditorMarshaller

It's possible to opt out of migration on view, for example if you would like to keep rendering the old parameters, and only use the new parameters when dealing with newly created macro to reduce the migration risk of new features.  This can be done by setting the excluded-schema-migration-points attribute on the macro module to view like this:

<macro name="contentbylabel" key="simplecontentbylabel" schema-version="2"
Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport