Hi everyone,
We would like to update you on some of the changes we’ve implemented to support migrating your Connect on Forge apps. These changes are part of an alpha release.
In order to allow you to replace your Connect app with a Forge version of the app, we have introduced an app.connect section in the manifest file so that you can reference Connect portions of your app. In particular, the app.connect.key will give you the ability to control the app key for testing your Connect on Forge app, and the app.connect.remote key will allow you to reference the baseUrl of your existing Connect app.
For example:
app:
connect:
key: hello-world
remote: connect-app-server
remotes:
- key: connect-app-server
baseUrl: https://hello-world-app.example.com
It’s important to note that the app.connect.key of your Forge app’s production environment should match the existing key of the Connect app you wish to replace. For development and staging, we recommend using the production key with a suitable suffix, e.g. hello-world.development . The tutorial linked below offers one way to juggle the different environments’ keys.
At this stage, changing the key is not supported, but support is coming soon.
If you have an existing Connect on Forge app you wish to continue using, you will need to set app.connect.key of its environments to match its existing (randomly-generated) key.
For more detailed instructions on how to configure the app.connect section, please see: https://developer.atlassian.com/platform/forge/build-a-connect-on-forge-app
As always, we invite you to share any feedback or bugs so that we can improve the migration journey from Connect to Forge.
Thank you 