add catalog-info.yaml file for forge catalog integration

[pham259]

Add a catalog-info.yaml file to root to be ingested in the Forge Catalog. Syncing can take up to an hour for it to populate in the table.

By default, the component will only be visible to the direct owner and Forge admins. If you want this component to be visible to others in the Forge Catalog, please update the visibility field to 'public'

Other attributes can be added/modified as well. Reference to the Backstage official docs

[lymereJ]

Thanks @pham259!

[lymereJ]

@pham259 - I thought that I could see the project on Forge a bit after the PR was merged, I can't see it now. I did change the visibility to public will Forge automatically change that parameter?

@weilixu - FYI.

[pham259]

@pham259 - I thought that I could see the project on Forge a bit after the PR was merged, I can't see it now. I did change the visibility to public will Forge automatically change that parameter?

@weilixu - FYI.

Responding here for transparency, It's an issue on our end. Our auto ingestion plugin wasn't set to discover repositories in GitHub pnnl (public) and initially was just setup for pnnl-int and pnnl-ext orgs within GitHub. We're working on adding discovery in other github orgs since there's a couple of other pilot repos that doesn't necessarily live in pnnl-int