Skip to main content

Hi,

 

Release 3.3.3 for the Mule Maven Plugin introduced the following new feature:

 

Added support for setting Object Store v2 and persistent queues configuration for CloudHub deployment.

 

Unfortunately, I have not found any documentation on how to specify turning on the Object Store v2 option at deployment time. I am finding that if a redeployment takes place using 3.3.3+, the Object Store v2 option will be disabled if not specified. This is a problem as data loose occurs when switching the implementations being used.

 

Looking at the source code for the Mule Maven Plugin, I would assume that you would need:

 

<configuration>

<cloudHubDeployment>

<uri>https://anypoint.mulesoft.com</uri>

<muleVersion>${app.runtime}</muleVersion>

<username>${username}</username>

<password>${password}</password>

<applicationName>${cloudhub.application.name}</applicationName>

<environment>${environment}</environment>

<objectStoreV1>false</objectStoreV1>

<properties>

<key>value</key>

</properties>

</cloudHubDeployment>

</configuration>

 

Is anyone able to confirm if this is correct?

 

Thank you.

1 respuesta
  1. 3 dic 2019, 08:57

    I was looking at the wrong GitHub model for the deployment. The CloudHubDeployment model contains:

     

    @ParameterprotectedBoolean

    objectStoreV2 =false;

     

    @ParameterprotectedBoolean

    persistentQueues =false;

     

    To ensure that Object Store V2 is used during deployment, set

     

    <configuration>

    <cloudHubDeployment>

    <uri>https://anypoint.mulesoft.com</uri>

    <muleVersion>${app.runtime}</muleVersion>

    <username>${username}</username>

    <password>${password}</password>

    <applicationName>${cloudhub.application.name}</applicationName>

    <environment>${environment}</environment>

    <objectStoreV2>true</objectStoreV2>

    <properties>

    <key>value</key>

    </properties>

    </cloudHubDeployment>

    </configuration>

0/9000