Feature ideas

The GitHub sync currently enforces a hard cap of 100 closed pull requests per repository (or those closed in the last 60 days) with no way to adjust. This prevents users from ingesting their full PR history and forces manual workarounds. We need to expose a configuration option or alternate mechanism to allow fetching beyond the 100-PR limit so that customers can ingest all closed PRs on demand.

Extend the OpenCost Ocean integration to include the /assets endpoint https://opencost.io/docs/integrations/api/#assets-api This would allow for more granular costings.

Today the GitHub tags importer only maps each tag’s name and commit SHA. We should add support for mapping the tag creation timestamp (e.g. the tagger.date field on annotated tags) into a property (e.g. tag_creation_date) on the Tag blueprint. This will let users sort, filter and report on tags by their creation time.

We have over 14k+ repos in our Port inventory at the moment. Only about a 1/4 are active (not archived). If we set the query in the selector to ".repo.archived == false", the GitHub integration pulls all repos, and then filters at the point of mapping. The list organization repos in the REST API (doc) doesn't support using the archive filter. But the search api (REST, GraphQL) allows active repos to be fetched using the following query: archived: false : https://docs.github.com/en/rest/search/search?versionId=free-pro-team%40latest&productId=search-github&restPage=searching-on-github%2Csearching-for-repositories&apiVersion=2022-11-28#search-repositories https://docs.github.com/en/graphql/reference/queries#search We would like the filter to apply before and not after (like it currently does). It would make the github integration faster and reduce load.

Port AWS ocean Exporter currently does not support extracting OpenSearch domain-type resources directly. While the AWS Cloud Control API supports CRUD operations for AWS::OpenSearchService::Domain, it does not support the List operation, causing the exporter to fail when ingesting data. An attempt was made to use kind:GetResourceAPI in the exporter selector, which uses Read instead of List, but the same error occurred.

It will be great to have an option in the values to have logging of port integration such as k8s, ocean and agent in JSON format.

It would be important to export the relevant data via Port Github integration, which says Dependabot security updates are enabled for a repository. Then that data can be mapped to a property (maybe a boolean) in the Repository blueprint.

Much like GitHub integration supports fetching Releases and Tags information for repositories (described here: https://docs.port.io/build-your-software-catalog/sync-data-to-catalog/git/github/examples/#map-repositories-repository-releases-and-tags ), it can be useful to get this information also from Gitlab. Releases: https://archives.docs.gitlab.com/17.10/api/releases/ Tags: https://archives.docs.gitlab.com/17.10/api/tags/

VM ware Ocean Integration