Heikki Hellgren
Heikki Hellgren
As well as this https://github.com/backstage/backstage/issues/10652
Maybe the plugin could utilize the event framework for the callbacks: https://github.com/backstage/backstage/tree/master/plugins%2Fevents-backend
So little update here. I've made a PR to backstage upstream to support sending stuff from backend plugins to frontend: https://github.com/backstage/backstage/pull/18153 This should allow further development for notifications in https://github.com/backstage/backstage/issues/10652...
A couple of new related issues in the backstage project: https://github.com/backstage/backstage/pull/21889 https://github.com/backstage/backstage/pull/22099 https://github.com/backstage/backstage/pull/21728
This is now done with backstage notifications system, closing!
It will take some time for the collator to run again and remove the question from search index. Same thing for other backstage collators like for the catalog; if you...
Depends how you have configured the collator (https://github.com/drodil/backstage-plugin-qeta/blob/main/plugins/qeta-backend/src/search/collators/QetaCollatorFactory.ts). It doesn't have scheduling as it's own. What search backend do you use? Do you have some cleaning for that?
I am not familiar with the `postgres` search backend, we use `opensearch` in my project and at least there we have to have a separate cleaner for the old documents...
Actually, this could also be shown in the ask question form and update the list when the user changes the inputs. But might be a different issue.