Changing app key when migrating to Cloud

Cloud Migrations
2

Hi @bbutnaru,

Thanks for your message. Let me try and answer it for you.

It sounds like the Listener is exported already as you mention getServerAppKey() is called in the Prepare your apps section. I suggest making sure you’re using Atlassian Spring Scanner 2 as a minimum, and having the Listener annotated as

@ExportAsService
@Named
public class MyDiscoverableListener implements DiscoverableListener {
...
}

Use dev-mode as this will ensure that the Listener is called regardless of its status in App Assessment stage.

As you already have a server app key, and it sounds like you have it registered in the Marketplace Migration API then this information may override your app key values in the Listener for App Assessment.

Along with dev-mode, I suggest that you use a new server and cloud app key (so yes, fork the code just for development), put them in getServerAppKey() and getCloudAppKey(). This will ensure that your development code will be called. Then when you’re ready to start production you can privately release a new version of the cloud app for testing.

I hope this helps.

Regards,
James.

3 Likes