Data Residency eligibility for Forge app making Fetch calls

Forge
1

Our Forge app uses Forge Fetch to make REST api calls to a non-Atlassian applications. We use wildcard domains in manifest e.g.

fetch:
      backend:
        - "*.google.com"
        - "*.microsoft.com"
        - "*.apple.com"

Are apps like this, that don’t use remotes, ineligible for pinning? This link states “Forge apps that don’t contain a remotes declaration automatically become eligible for PINNED status.” But this one seems to state the contrary.

If we do need to make changes to become eligible for pinning, what’s the best way to migrate above manifest to use remote? Our app connects to multiple systems and the full URL is not available to set in the remote’s baseUrl parameter.

2

The Forge Data residency doc is in a bad state, to stay polite.

You need to modify your fetch.backend part to use the remote syntax, something like:

fetch:
      backend:
        - google-remote
        - ms-remote
        - apple-remote
...
remotes:
  - key: google-remote
    baseUrl: "*.google.com"
    operations:
      - fetch
  - key: ms-remote
    baseUrl: "*.microsoft.com"
    operations:
      - fetch
  - key: apple-remote
    baseUrl: "*.apple.com"
    operations:
      - fetch

For the values of operations, it is vaguely documented here: https://developer.atlassian.com/platform/forge/manifest-reference/remotes/#data-residency

You might (must ?) also need the inScopeEUD: false part.

4 Likes
3

Thank you for the clarification.