Project Catalog represents curated resources relevant to people outside the project. In my view there are a few items missing which are particularly relevant when the project becomes rather large:
Data connections
List of sensitive resources
Changes in security permissions in resources
Benefits:
With the information displayed as below, the benefits are:
Changes in security and Org markings would be immediately surfaced to Owners of sensitive resources coming from upstream projects.All with one-click without delving into large code basis or unfamiliar project folder structures.
Decommisioning, Exports and Support associate to that Data Connections: In large projects, users loose track how many data connections are in place and exports. Many data sources are also no longer in use. One can unfold the data lineage but it is rather tedious.
Workarounds:
All this metadata is possible to retrieve through the right endpoints. However, the backend API endpoints are not documented nor supported.
I agree with you that the retrieval of this metadata is too difficult today in the platform. What are all the types of metadata that you would like the platform to provide to you?
For this specific request, do you think putting this information is the right level of abstraction? I worry that for people who care about where sensitive data is being user they would find it cumbersome to click into each and every project to see this information.
Hi @owen – appreciate your attention to this. I’ve also suggested that this info could live in a separate app, though I don’t have full UX or product context.
From my perspective, the key abstractions are projects, portfolios (which group related projects of an application), and spaces. I believe this data should be at least visible in both the project catalog and portfolio overview, enabling 1) platform admins to federate these tasks, and 2) app owners to manage it more effectively (see example below).
While the project catalog can feel cluttered, there’s space in the sidebar for a dedicated tab, which could keep things clean. As for the amount of information, one could introduce pagination. The Data lineage doesn’t render more than 500 items at once. One needs to expand it. The same principle could be applied to show all resources in case there are that many.
