Can I use Forge resolver function from my adopted connectModules (using @forge/bridge) invoke?

[Oleh Kosar]

I mean is it possible to use manifest like this:

app:
  id: ari:cloud:ecosystem::app/xxx
  connect:
    key: com.xxx
    remote: connect
    authentication: jwt
  runtime:
    name: nodejs20.x
  licensing:
    enabled: true

remotes:
  - key: forge-remote
    baseUrl: '${REMOTE_APP_URL}'
    operations:
      - compute
      - fetch
    auth:
      appUserToken:
        enabled: true
  - key: connect
    baseUrl: '${REMOTE_APP_URL}/sample'

modules:
  function:
    - key: connect-resolver
      handler: connect-resolver.handler


connectModules:
  jira:adminPages:
    - url: >-
        /plugins/servlet/sample?isAdmin={condition.user_is_admin}&startScreen=rest-api
      key: rest-api-page
      name:
        value: REST API
      location: admin_plugins_menu/sample-admin-section
      conditions:
        - condition: user_is_admin
      weight: 500
      resolver:
        function: connect-resolver

  jira:translations:
    - paths:
        de-DE: /i18n-cloud/de.json
        fr-FR: /i18n-cloud/fr.json
      key: connect-translations
  jira:cloudAppMigration:
    - migrationWebhookPath: /br-migr-event
      key: app-migration
permissions:
  scopes:
    - read:connect-jira
    - write:connect-jira
    - delete:connect-jira
    - act-as-user:connect-jira
    - access-email-addresses:connect-jira
    - admin:connect-jira
    # forge scopes
    - read:app-user-token # for 'forge-remote'
    - read:jira-user # for rest/api/3/myself
    - storage:app # kvs.get and kvs.set

[Tuncay Senturk _Snapbytes_ · Accepted solution]

Hi @Oleh Kosar 

Unfortunately, you can’t call a Forge resolver from an adopted connectModules page.

invoke() only works when your frontend is running inside a Forge UI runtime.

However, the best place to ask developer questions is the Atlassian Developer Community.

[Oleh Kosar]

Thanks for answering @Tuncay Senturk _Snapbytes_

Confused these 2 communities :)

Best Regards,

Oleh