Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Periodic catalog database reset?
See original GitHub issueAt our company, we use (a slightly changed version of) the github-discovery plugin to add entities to Backstage. In some specific cases, we noticed that some issues were introduced in the Backstage ‘state’:
- An entity was manually deleted (and apparently not picked up anymore by
github-discovery) - The main branch of a repo was changed and changes to the entity were not picked up anymore.
Of course specific issues like these could be tackled, but since the catalog is set to readonly, we would also be happy with having a periodic reset of the database. Right now that is at least how we fix these kinds of issues.
We were wondering if there is the possibility of a periodic (nightly) reset of the database. I think the ingrediënts are there, but we lack the required knowledge right now.
Possible Implementation
A combination of the recently added TaskScheduler and some knex logic?
Other ideas? Perhaps we are not thinking correctly about this issue. Help is appreciated!
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It seems that the latest version indeed fixes both issues. Note that for the Github main branch change to be picked up, it is necessary to both delete the entity and the corresponding location.
Thanks for opening a new issue, @Rugvip. And for the support! Closing this issue is fine by me, since the root causes are fixed now.