We have a situaltion here, where we have released out connect on forge app. however the connect framework was not upgraded to latest and we missed table “atlassian_host_mapping” entries. Now most of our clients have already upgraded to forge, however i do not have entries in this table. i understand that this mapping is done with /installed hook.
How can i insert the entries in this table? i tried sending scheduled trigger to connect but only information i get it installationId from the request. how do i get the clientKey as well?
Thanks for the clarification, that’s good - it will make things easier.
Connect on Forge apps won’t resend a lifecycle event for a minor update, but there is a way for us to invoke a major update, roll it out to users and receive an updated event.