Issue with Forge remotes and "Runs on Atlassian" program

[Daniel Platas]

Hello,

I'm struggling to find a proper solution to become compatible with the "Runs on Atlassian" program while keeping my app capabilities, due to what appears to be inconsistencies in the Forge manifest behaviour.

I have this Rovo agent that fetches public documentation from my company's instance to help guide users -- this doesn't involve customer data, so it should still be compliant with the RoA program baselines. To add permissions to this operation, I set up this "remote" attribute in my `manifest.yml` file, according to this documentation:

permissions:
  external:
    fetch:
      backend:
        ...
        - remote: "remote-docs"
remotes:
  - key: remote-docs
  baseUrl: "https://docs.adaptavist.com"
  operations:
    - fetch

This is looking all good; however, it doesn't work. This is a message running `forge eligibility -e development` after deploying:

ℹ The version of your app [8.0.0] that's deployed to [DEV development] is not eligible for the Runs on Atlassian program.
- App is using remote services
- App is egressing data

Is this a bug in the manifest configuration? Am I missing something?

On the other hand, I've successfully managed to make this work by using the config:

permissions:
  external:
   fetch:
     backend:
     ...
     - address: "docs.adaptavist.com"
       category: "analytics"
       inScopeEUD: false

Although I can guess this is not very orthodox, can I use this as a workaround if the previous, official way is suffering from a bug or is not expected to work at all for some reason?

Thanks in advance.