Is there a way to figure out the old connect app info when upgrading to Forge

Forge
,
1

Hello,

Could you please help me figure out how I can identify the info for the matching connect application instance while processing the “avi:forge:installed:app” event generated when upgrading from connect to forge?

Thank you

2

Hi, assuming you are using atlassian-connect-express, and your server receives both the connect webhook, then the forge event, you can use associateConnect as explained here. atlassian-connect-spring-boot offers a similar affordance, and you can inspect the source as a reference if you have a bespoke Connect implementation.

3

Hi,
The Forge event installation contains the cloudId of your site. And on Connect side, you can get the `cloudId with a request to https://your_site.atlassian.net/_edge/tenant_info

And if you use Forge-from-Connect, the Connect installation payload contains 2 new properties: cloudId and installationId

4

Hello,

Thank you @jhazelwood and @SilvreLestang for taking the time to help me with this issue. After reviewing the code in atlassian-connect-express and thinking on the proposed workarounds, I realized that I was missing something.
When we moved to Forge, we decided to start ‘clean’ and so we mainly disregarded the converted manifest. And since all our Connect modules were moved to Forge (with remotes), we did not realize that we actually still needed the:

connectModules:
  jira:lifecycle:

After adding this module, I now receive the installed event in the Connect app with the clientKey and installationId fields.

Thank you

1 Like