We need to extend the scopes required by our Confluence Cloud app, and AFAIK all our existing customer will need to approve this update on their cloud instances manually.
We don’t expect all our customers will approve this update quickly or even approve it at all. The problem with it that we can’t deliver descriptor updates to such customers after new version with extended scopes set will be released. It might be required if we add a new module (which works with both sets of scopes) or need to refactor backend endpoints.
Is it possible to maintain two versions of descriptors for both sets of scopes? Is there any workaround if the straight way doesn’t exist?
There is a related topic (but it doesn’t answer my question) - How to handle connect add-on upgrades that require manual customer approval?