Feature ideas

Currently, the webhook integration does not allow you to reingest failed events, or recover from incidents with the integration. Implementing a Dead Letter Queue or an alternative mechanism that lets you redeliver events received by the webhook integration will improve the integration resiliency.

For some kinds available in integration, the API responses can vary greatly depending on certain conditions. As a concrete example, in the github integration, the branch kind only contains properties like .branch.commit.commit.author when the branch is the default branch of a given repository, and in my mapping I set the query to .branch.name == .repository.default_branch to ensure I have access to that value. What I'm currently finding is that the sendRawDataExamples option in integrations does not respect this query setting, so the ~5 examples retained from the api call might not even contain a valid api response (as in, one that passes the check in query ). I have a few varied suggestions here: Allow sendRawDataExamples to respect the given query in a mapping. Allow sendRawDataExamples to have it's own query for stricter or looser example api responses. Allow independent resync of sendRawDataExamples separate from a resync of the data source. Giving builders the ability to have stronger control over the examples defined in the data source view would significantly improve iteration time when dealing with complex mappings across multiple data sources.

Support pulling from Github's dependency graph https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph which would enable us to do in-depth analysis of all the software dependencies for the repositories we have in Port. There is already a REST api for it: https://docs.github.com/en/rest/dependency-graph/sboms?apiVersion=2022-11-28#export-a-software-bill-of-materials-sbom-for-a-repository Use cases for having dependencies catalogged in Port Track usage of internal packages and how up-to-date consumers are, either through dasboards or scorecards Build comprehensive documentation around service dependencies Build automations/self-service actions around notification for migrations, deprecations, releases with breaking changes, targeted towards the proper teams instead of everyone Detect inefficiencies/antipatterns related to dependencies Enforce standards/protection measures related to dependencies (ensure no-one uses package X, ensure everyone uses package Y at least at version A.B.C, etc.)

When installing an integration from the data sources modal, it would help to have a search box to make it easy to find the desired integration.

Today, when updating new objects / arrays of entities the new value overrides the old one. With this feature it will be possible to append values to these properties. Example of Tags property with type of array: Current state: "Tags" : ["tag1"] Ingesting a new tag using the API: "tag2" New state: "Tags": ["tag1", "tag2"]

Currently, you can update the integration mapping config and default blueprints through the ocean integration after deploying. Adding the option to provide those as parameters in the helm chart could make the process of deploying integrations faster and better.

I want to be able to insert entities by batch or bulk through webhook/REST api to prevent calling the same endpoint many times. I also want to be able to do the same when deleting entities. Having checkboxes in catalogs to select and do a specific action for selected entities can also help :)

When visiting a specific page in Port I would like to automatically trigger the (re)sync of a specific data source. Currently my option is to manually resync it from the Builder page, or start a Self service action to trigger it.

The Port GCP BigQuery data source only contains a subset of the fields available in https://cloud.google.com/bigquery/docs/reference/rest/v2/tables . Some useful fields that are currently missing in Port are: - column metadata (from https://cloud.google.com/bigquery/docs/reference/rest/v2/tables#TableSchema - including name, description, type and any policy tags) - numRows - lastModifiedTime Why: I'd like to use Port as a Data Dictionary, and so it will be useful to have as much information about tables as possible.

Add option to specifically resync a predefined list of resources & do a scheduled resync only for a selected list of resources