Hi Community,
we are currently preparing a major release of a Confluence Cloud Plugin. This makes it necessary to
- change the baseURL (subdomain) of the API
- change the URL (subdomain) of the atlassian-connect.json
So far we published the plugin as private and we are able to install the plugin using a Private Listings Token and it is working fine.
in order to generate a smooth experience for the users we would like to accomplish a way of being able to update from the current plugin version the the new version without the need to uninstall. So what we were trying is:
- Install the plugin from the marketplace in its current public version
- Insert a token from the private listings so the private updated version becomes visible and the plugin manager offers the Update Button
- When clicking the button the plugin Updates smoothly and the new features become available
The last part is failing currently so we are not able to test the update experience for our users. Or the result of the test is that it is not updateable the way we intent but we do not understand why.
Investigating the documentation we did not find a definite guide to answer the following questions:
- can a public plugin be updated to a privat version via Private Listings Token without uninstalling? (Isn’t that exactly one purpose of Privat Listings and private versions?)
- what changes to the atlassian-connect.json require a definite re-installation of the plugin (besides the obvious “key” properties)? Any blocker here?
- is the approach to change the baseUrl, change the url of the atlassian-connect.json, pump up the apiVersion for a version → publish as private version in order to test the update ability and the new features, a correct way?
I am grateful for every suggestion or a pointer to a helpful part of the documentation.