core:connectToForgeMigration module questions

Forge Forge Modules and Product Triggers
1

I noticed the changelog about the core:connectToForgeMigration module and had a few questions.

@EshaaSood, tagging you since you were driving the initial RFC for this.

The changelog mentions:

Apps with public Marketplace listings will remain unaffected. However, we encourage you to add this module to your production app, so you can receive the updated behaviour as soon as it goes live.

  1. Is this module GA and can/should be used by all apps with Connect history?
  2. We have a public Marketplace app. Can we safely add this module today without creating a major version when deploying and backporting to previous major versions?
  3. Is there any benefit to adding this to the Forge-only app version, or does it only make sense for Connect-on-Forge versions?
  4. The RFC includes comments on Connect and Connect-on-Forge messaging. Does Atlassian already have a clearer idea of what the messaging and outreach looks like to get admins to upgrade their installations?

Thanks!

2

Anyone from Atlassian who can help with these questions?

3

@EshaaSood, could you please help with the questions above?

I think I roughly understand 3 and 4 now (please correct if I am wrong). Remaining Qs 1 and 2, is this GA, and can you confirm that this does not create a major version?

Regarding 3: While it does not really make sense to add this module to a pure Forge app, that is the mechanism that Atlassian picked to control the migrationGuideUrl and willMigrateToForgeBeforeEOS boolean value. Is this correct?

Regarding 4: Based on the accidental rollout last week, I assume this means the Connect messaging will be driven by the information (link and boolean) provided in the Forge module?

4

Hey @tbinna

Thanks for your questions and apologies for the delay, this got lost in my inbox post TEAM.

  1. This module is not GA yet. It is currently only available for those enrolled in the Developer Canary Program and will only show for those with private apps. Once this is available for partner testing, I’d recommend utilising this module if you currently have an app that has a Forge manifest with Connect modules in it. Messaging to customers will only appear if an app has components running on Connect.
  2. That is correct, introducing this module in your manifest will not trigger a major version update
  3. If you have removed all Connect modules and scopes and run entirely on Forge (including with remotes), you won’t need to utilise this module as messaging will not appear for customers. This also applies to any Forge native or Forge RoA apps. However, if you have a manifest with Connect modules, this is when the module should be utilised.
  4. If we detect that an app is not running on the latest version, we will prompt the admin to update their app in the messaging. In addition, we will also display to admins the information you have provided with the module

We have some docs available here for the private app experience if you’d like more information on how it will work.

5

Thank you for the clarification, @EshaaSood. We will be eying the changelog for a Preview/GA announcement.