Slightly leading question
BUT please be aware that it would have to be version dependent. Is somebody could have been running a version that is 6months old. During that time the cloud version has moved on and the info that might have been uploaded might not be enough (ie the user would have to upgrade the plugin to the latest version.
OR in some cases - the upgrade might not either work or be possible at which point the framework needs to show the appropriate steps.
Unlike Atlassian we don’t necessarily have all of that knowledge ahead of time (the version matrix would be insane - just thinking of the version combinations possible on jsw).
All of that said - if we had a module type that could define an interface where we can just handle the upgrade bits (with some type of transaction support over http) it would make it a lot easier for vendors to support. If this existedthen this would also be an awesome way to embed instructions for when manual interventions would be necessary (ie don’t have an external webpage).
The other gotcha though is (like I mentioned up a bit) is that we’d probably need to have an opt-in list for various versions - ideally on the marketplace so that we can easily kill the support on a per version basis after release (also has the benefit that you can use that to flag to customers about support).