Connect to Forge: connectToForgeMigration module in the first Connect -> Forge release?

Forge Adopting Forge from Connect
1

Hi everyone,

We’re preparing the first Forge version of our Connect app, i.e. the release where our Connect descriptor is replaced by a Forge manifest for the first time. The manifest is a straight conversion via connect-to-forge convert with all functionality staying in connectModules, so we expect the Connect → Forge update to be a minor (non-admin-approved) one.

We’d like to declare connectToForgeMigration right in this first version, so that admins start seeing our migration plan instead of the generic Connect EOS warning as early as possible, without waiting for a later release.

Our reading of the docs is that this is fine: the module page says a Forge manifest is enough without a full migration, the minor update criteria say adding Forge modules doesn’t require admin approval for the initial Connect → Forge update, and this thread confirmed the module doesn’t trigger a major version. Since the first production deployment is hard to undo, we’d appreciate a confirmation for this exact case:

  1. Is declaring connectToForgeMigration in the very first Forge version (the one replacing the Connect descriptor) supported, without affecting the initial update being classified as minor and rolled out automatically?
  2. Is there any Marketplace-side reason to keep the first Forge version limited to the converted Connect content and add the module in a later version instead?

Thanks!

2

The declaration of anything in the “modules” section of your manifest will always be treated as a minor version update. If you don’t get automatic updates then it will be because of something in your permissions: and to fix that you can just lower permissions with the next deploy and automatic updates will work.

On that specific module, I would highly highly recommend you add it to all versions of your forge app until you have no connect modules left.

3

Thanks, that’s really helpful! We’ll keep the module in every version until no Connect modules are left.

To clarify what I was trying to understand: can the very first Forge manifest, the one that replaces the Connect descriptor, contain at least one Forge module in the modules section, even if it’s just connectToForgeMigration? Or does that first version have to contain only Connect modules in connectModules, with any Forge modules added starting from the next version?

Your recommendation to add the module to all versions suggests the first one is fine too, but I’d like to be sure there’s nothing specific to the initial Connect → Forge transition that requires a Connect-only manifest.

4

There is no restriction or limitation for modules. That first version can contain all connect modules, or all forge modules, or anything in between.

We have watched many different apps migrate already and take many different paths with their modules and all have been successful.

5

Hi @rmassaioli , we backported and deployed the connectToForgeMigration module to our older major version (V2) that had connect modules. Our latest version (V3) has only forge modules.

connectToForgeMigration:
    - key: ctf-migration
      migrationGuideUrl: https://support.mycompany.com/path/to/info
      willMigrateToForgeBeforeEOS: YES

In app management > connected apps the warning message for a production site on V2 says:

(!) This app version is running on a platform that will be unsupported soon. Update your app now, as the latest version could provide better support options or a migration path. For more details, read **[Connect End of Support: What it means for Marketplace apps]

My understanding was the support link to migration url was supposed to be shown.

Is this expected or a bug? It is disconcerting to our customers because they cannot see the link to the migration guide.

Thank you
Chris

6

Hi @Chris_at_DigitalRose, this message is expected - when there’s a new version available, we prioritise this message What admins see on the Connected Apps page to encourage admins to upgrade to the latest first.

Once admins updated the app to the newest version and the app has connectToForgeMigration with YES, they will see this message ( What admins see on the Connected Apps page ) with the migration url in there.

7

Thanks for clarifying. It is a puzzling direction though.

We’ve had a 100% forge version out for 3 months now but are still fielding customer support requests for a migration guide. Our customers are focused in the compliance space, and they are looking for more information before updating.

It is not helpful for our customers to raise the threatening warning message and withhold the migration guide that would help reassure them and/or explain the permission and scope changes necessary for forge. It is a ‘curious’ design decision to expect customers to update and approve the new release and only after that show them the guide… Showing the link doesn’t block the update.

How is the migration guide presented after the update. Is it persistent and accessible by the admin or is it a flyby popup? (We have one “clean” prod site with a marketplace install of our legacy connect version; concerned if we update it we may never get it back)

Thank you
Chris