Feature ideas

Today the K8s exporter is able to take a single event/object from the K8s API and create a single entity from it based on the configuration attached to the exporter in Port. In the case of some CRDs (for example, those from Trivy), the CRD itself gets updated overtime with new information, which is stored as an array on the CRD. To make it possible to create multiple entities from the array stored in the CRD, it is required to add a configuration to the K8s exporter that is similar to the itemsToParse ( https://docs.getport.io/build-your-software-catalog/sync-data-to-catalog/webhook/#structure ) capability that currently exists in Port's generic webhooks

Currently the list pull requests api doesn't return the same data as when performing specific GET request to pull request ( e.g. merged, mergeable etc.. properties are missing ) Seems like Github API has a graphQL which supports more properties for resources and advanced search capabilities. https://docs.github.com/en/graphql/reference/objects#pullrequest https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#list-pull-requests

Prometheus often contains a lot of valuable data that we would want to expose to developers via Port, e.g. SLIs like performance, uptime, error rates, costs, alerts It would be nice if Ocean had an integration where we could configure PromQL queries that it could execute periodically and map results back to Port entities

Current Behavior: The file kind type currently does not support dynamic file paths for importing file content into a port. This limitation restricts flexibility when dealing with multiple files or varying file locations. Proposed Change: Enhance the file kind type to support dynamic file paths, similar to the functionality already implemented in port YAML. This change will allow each document processed as file-kind mapping to specify a different file path, providing greater flexibility in file content import. example importing swagger spec in git-ops fashion: interfaces: - name: Petstore openApiSpec: file://petstore.yaml - name: Data Set API (DSAPI) openApiSpec: file://../dsapi/uspto.yaml The expectation from mapping this file would be to create two interface entities which have a swagger tab containing the specified OAS files.

VM ware Ocean Integration

Currently, when multiple port.yaml files update the same entity, the relations array gets overwritten by the latest update, and any existing relations are lost. It would be helpful if relations from all port.yaml files can be aggregated to maintain a comprehensive list of relationships across projects.

Give me the ability to declaratively define my Port desired state (e.g. blueprints) as k8s resources in yaml. That I can commit to a git repo and have a GitOps tool like ArgoCD automatically pull and submit to k8s. Have a Port k8s controller that installs the required port CRDs to said cluster and when ArgoCD syncs the resources to the k8s cluster the Port controller reconciles the desired state to the actual on app.getport.io Outcome is that we have a declarative versioned state of our Port instance that can be manged and applied following GitOps principles. A "Port" control plane within k8s if you like. A bit like how Crossplane can be used to manage external cloud resource state.

Splunk Integration: We would like to see the events recorded in Splunk against our services. Details about each event should include its name and code, dimensions, timestamps, category, any properties, as well as a link to the original item in Splunk.

Having a built-in feature to sync Port’s service catalog directly with incident.io would be beneficial, as it would help in removing the dependency on external CI/CD pipelines.

Allowing data fields like comments, review_comments, commits, additions, deletions, and changed_files in the pull request exporter of the GitHub integration would help measure pull request standards.