Handle Jira Connect installation updates
What does this MR do and why?
This controller handles lifecycle hooks that are coming from the GitLab for Jira app.
The previous logic ignored installed hooks when the installation already exists. This was because we assumed that the hook would only indicate an App version update, but don't need to be processed.
It turns out installed hooks for existing installation are aiming to update those installations with a new auth token or base_url. Read more about this here
On 2022-03-10 Atlassian rolled out new auth tokens for existing installations as part of this change. GitLab couldn't handle the webhooks correctly and missed updating the tokens, resulting in broken installations.
Related issues:
How to set up and validate locally
I couldn't find a good way to validate the behavior locally because installed hooks need to be triggered by Atlassian.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.