Hello everyone,
I’d like to know if someone could help us identify the configuration issue we’re facing with Data Residency in a Connect-on-Forge app. We are currently trying to migrate data from Connect to Connect-on-Forge. However, during the Data Residency migration, we are not receiving any migration requests on our backend.
Our configuration in the manifest is as follows:
- Data Residency configuration
modules:
migration:dataResidency:
- key: dare
remote: connect
path: /data-migration
maxMigrationDurationHours: 2
- Data Residency endpoints
remotes:
- key: connect baseUrl:
default: "https://${PTK_DOMAIN}"
US: "https://us-${PTK_DOMAIN}"
EU: "https://${PTK_DOMAIN}"
operations:
- storage
- compute
- fetch
storage:
inScopeEUD: true
Our configuration in the atlassian-connect file is as follows:
- Data Residency configuration
"lifecycle": {
"installed": "/installed",
"uninstalled": "/uninstalled",
"enabled": "/enabled",
"disabled": "/disabled",
"dare-migration": "/data-migration"
},
"dataResidency": {
"maxMigrationDurationHours": 2,
"realmPersistenceDays": 30
}
- Data Residency endpoints
"regionBaseUrls": {
"Global": "https://${addon.base-domain}",
"US": "https://us-${addon.base-domain}",
"EU": "https://${addon.base-domain}"
},
Our controllers in the backend side:
@ForgeRemote(associateConnect = true)
@PostMapping("/data-migration/start")
@AllowAnonymousUser
public ResponseEntity<DataMigrationResponse> handle(@RequestBody DataMigrationStartRequest dataMigrationStartRequest) {
log.info("DataMigrationStartPostController start. Request: {}", dataMigrationStartRequest);
try {
dataMigrationStarter.handle(dataMigrationStartRequest.migrationId());
} catch (DataMigrationException e) {
....
}
....
}
Do we need to add the @ForgeRemote annotation in the migration controllers? Is there anything else we should take into account when setting up the configuration?
Thanks in advance!