Feature ideas

Currently, multi select ENUM is only supported by configuration from the UI and API. Adding support for IaC will allow better configuration of the Portal via code, matching the capabilities in the API.

Currently, when searching for related entities, all related entities in the blueprint specified will be returned. This feature will allow for the specification of the relation path, allowing different visualizations to be based on it. For example, Create separate tables for 2 types of relations to the same entity.

Add pagination to the Port API.

Integrate jq/yq support into Github Mapper for advanced file processing. This feature would allow users to directly query and manipulate data from files like JSON, YAML, and similar structured files using jq/yq syntax. For instance, users could extract the PHP version directly from a composer.json file or a Dockerfile without the need for additional calculated properties or complex parsing logic.

Currently, the "entity JSON example" section in the JQ playground is automatically filled with dummy data according to each property type. We would like to provide in that section the option to get real data from the catalog in addition to the dummy data option. In addition, we will add support for "YAML" property to convert YAML data into JSON to be used in the JQ calculation.