Forge data residency hook comes to wrong base URL

Forge
1

We are testing data residency in Forge. The manifest includes the following:

remotes:
  - key: connect
    baseUrl:
      default: https://test-host-1.dev.structure.app
      US: https://test-host-1.dev.structure.app
      EU: https://test-host-2.dev.structure.app
      DE: https://test-host-2.dev.structure.app
...
modules:
  migration:dataResidency:
    - key: dare
      remote: connect
      path: /atlassian/structure/realm-migration
      maxMigrationDurationHours: 2

In the Security/Data Residency admin, we can see that the Forge application is installed in Germany, i.e. the active base URL is https://test-host-2.dev.structure.app (we can also see that EU, Germany, USA are supported) and we can see that requests from the UI go to this host. At the same time Jira itself is pinned in USA.
But when scheduling a migration of plugin data from Germany to USA, the webhook comes to the path /atlassian/structure/realm-migration/schedule of the host https://test-host-1.dev.structure.app, not https://test-host-2.dev.structure.app.

4 Likes