Issues getting blank forge app deployed (intern)

Hey folks! One of the tasks for my intern project is getting a blank forge app deployed. I’ve been running into issues so far, and some help and guidance would be much appreciated. :slight_smile:

Current errors (this is after going through the forge setup/readme file getting up to the point of deploying):


Hi @DanicaTalbot ,

Welcome to the Atlassian Developer Community.

It looks like your app is referencing component-page somewhere, but the file doesn’t exist. Can you share your code and manifest.yml.

Dugald

1 Like

Hi @dmorrow!

here is my manifest.yml file:

modules:
  compass:componentPage:
    - key: airflow-integration
      resource: vnext-data-catalog 
      resolver:
        function: catalog-resolver
      title: Airflow
      icon: https://en.m.wikipedia.org/wiki/File:AirflowLogo.png
  
  compass:dataProvider:
    - key: data-provider
      function: data-provider-fn
      callback:
        function: data-provider-callback
      linkTypes:
        - other-link
      domains:
        - 'microscope.prod.atl-paas.net'
        - 'microscope.staging.atl-paas.net'
  
  
  function:
    - key: catalog-resolver
      handler: component-page.run
    - key: data-provider-fn
      handler: index.DataProvider
app:
  id: ari:cloud:ecosystem::app/b38e5a48-53a8-4816-8b77-2e2029c5a993

resources:
  - key: vnext-data-catalog
    path: ui/build/component-page
    tunnel:
      port: 3001

permissions:
  # For more info on manifest permissions, see https://developer.atlassian.com/platform/forge/manifest-reference/permissions/
  scopes:
    - read:component:compass
    - write:component:compass
    - read:metric:compass
    - write:metric:compass
    - read:event:compass
    - write:event:compass
    - storage:app
    - read:scorecard:compass
    - write:scorecard:compass
  content:
    styles:
      - 'unsafe-inline'
  external:
    fetch:
      backend:
        - compass-data-connector.dev.services.atlassian.com
        - compass-data-connector.services.atlassian.com
        - compass-internal-syncer.dev.services.atlassian.com
        - compass-internal-syncer.stg.services.atlassian.com
        - compass-internal-syncer.services.atlassian.com
      client:
        - https://production-01-airflow-01.socrates.atlassian.com
        - https://airflow-ui-redirector.us-east-1.prod.atl-paas.net
        - https://manager-service.us-west-2.prod.atl-paas.net
        - https://manager-service.us-west-2.staging.atl-paas.net
    frames:
      - 'https://api.stg.atlassian.com/'
      - 'https://production-01-airflow-01.socrates.atlassian.com/'
      - 'https://airflow-ui-redirector.us-east-1.prod.atl-paas.net/mwaa'
      - 'https://manager-service.us-west-2.staging.atl-paas.net/'
      - 'https://manager-service.us-west-2.prod.atl-paas.net/'
      - 'https://microscope.staging.atl-paas.net/'
      - 'https://microscope.prod.atl-paas.net/'
      - 'https://7a943829-e3e4-4f7b-a87c-0e2b3dcd5c8d.cdn.stg.atlassian-dev.net/'
      - 'https://f8e96330-d662-4895-bb7c-0d1206ac4457.cdn.prod.atlassian-dev.net/'

Hi @DanicaTalbot ,

It looks like component-page.jsx needs to be moved to within the ui part of your source code hierarchy - maybe within src/ui/component-page.

Dugald