While working on #101 we found that one of the repos has been handed over to a different owner, that makes us create a request to get the stars of repo "X" and getting the stars for the new repo "Y".
Since we are creating bulk requests to github, we are unable to know which is the changed repo.
When this happens, the whole application fails to start.
the solution we came up with is to create a sanity check job that makes sure that no repos of the current resources has been moved.
We can also add to it more tasks to check the existence of the container image and the repo
that job could be run periodically and be a prerequisite to deploying to prod.
Parent Epic: #207
While working on #101 we found that one of the repos has been handed over to a different owner, that makes us create a request to get the stars of repo "X" and getting the stars for the new repo "Y".
Since we are creating bulk requests to github, we are unable to know which is the changed repo.
When this happens, the whole application fails to start.
the solution we came up with is to create a sanity check job that makes sure that no repos of the current resources has been moved.
We can also add to it more tasks to check the existence of the container image and the repo
that job could be run periodically and be a prerequisite to deploying to prod.