Am I right to understand that if the app enrolls in this program, if it moves to fully Forge on the second/subsequent update (and as a result removes Connect remotes), it still requires admin approval? As this is mentioned in the table here - Minor version updates (Connect to Forge) (Preview), where it lists that “Removal of the remote used for Connect” will require admin approval.
What is the logic behind this? As this does not really solve the issue where the marketplace partners have to keep both versions running, as the Connect remote version will be still used, until everyone upgrades, and the only way is to go full Forge on the first update.
As per RFC-71, there are two key components we are delivering:
The Connect to Forge migration, which is now in Preview and opt-in for the reason you’ve noted. If an app wanted to, it could deliver the first version on Forge with Connect remotes and then remove them in a subsequent version prior to opting in for minor updates. This would mean that all existing customers would be moved to the most recent Forge version which does not include the remote.
The Forge to Forge migration, which is in development. This will provide a similar mechanism through which the app can perform minor updates from earlier Forge versions to more recent versions, where there has not been an elevation of permission (i.e. a removal of remotes or scopes, or inherited scopes)
@SeanBourke, in your example, if an app would deliver the first version on Forge with Connect, it will then require a major upgrade and only the second would be minor, wound’t it?
Regarding the Forge to Forge migration, so I understand this will be implemented at some point in the future, where only the elevation of permissions requires a major upgrade, right?
Our goal is to go from full Connect to full Forge. Ideally, we would be doing this in two stages, first just using converted manifest without any Forge functionality, and the second is to all the full Forge modules and Connect remote removed. So please confirm if my two assumptions are correct:
This is not possible to achieve without major upgrade on one or the other of the stages, even with this preview program (with no elevation of permissions).
This is possible to achieve if going in one stage from full Connect to full Forge if no elevation of permissions exists.