hard lotus
I’m trying to implement a entity provider to collect app list inside organizations, but I want to enable developers to add their own info by adding catalog-info.yaml in GitHub, is that a good practice?
Also is there any embedded yaml parser in this project? It should be present somewhere, or those yaml cannot be stored, but where can I find it!
heady owl
We actually do that as well. We use gitlab as the place where developers can add their catalog-info.yaml files, and then we use Consul to inject more info, such us where the component is deployed, where it's found (urls, etc), the current version and other things
You can use a CatalogProcessor to only handle those custom entities
hard lotus
Are these catalog-info.yaml discovered by GitHub catalog plug-in or you implemented it from scratch?
heady owl
We are using the GitlabProvider, the native implementation from backstage. We just created the custom processor to inject more info to those entities
hard lotus
thank you, that’s a good point!
I’m still considering provider instead of processor, I have an existing platform, which already has a list of bunch of apps, integrating with it would bring many catalog to backstage immediately, which is good.
But the potential problem is that this could conflict with GitHub/Gitlab discovery as catalog-info.yaml would be discovered by GitHub discovery once again. If there’s some kind of “auto-merging”, that would be great.