endpoint parameter support in custom content

XMLWordPrintable

    • Minor

      Issue Summary

      As per Confluence custom content  {{

      {endpoint: string}

      }}is valid, but when we try it in manifest.yml, there are parsing errors.

       

      259:2 error confluence:customContent should NOT have additional property 'resource' valid-document-required 
259:2 error confluence:customContent should NOT have additional property 'resolver' valid-document-required 
259:2 error confluence:customContent should NOT have additional property 'migratedFromConnect' valid-document-required 
259:2 error confluence:customContent property resolver should NOT have additional property 'endpoint' valid-document-required 
259:2 error confluence:customContent required properties are 'title, supportedContainerTypes, function, key' or 'title, 

supportedContainerTypes, resource, key' valid-document-required

       

      Steps to Reproduce

      1. While trying to use remote endpoint in the custom Content module hitting into  errors

       
       

       
confluence:customContent:
    - key: customC1
      title: Custom
      resource: mainPage
      icon: resource:images;icon.png
      resolver:
        endpoint: remote
      supportedContainerTypes:
        - space
      indexing: true
      migratedFromConnect: true

      Expected Results

       
       endpoint: <remote-endpoint>
      This is currently documented as valid in the Confluence custom content module and should work as expected.

      Actual Results

      Errors while Forge deploy

      Workaround

       Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              Ramachandran N
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: