Feature ideas

We have noticed that a number of changes in GitHub do not trigger a change in Port. For instance we archived a repo and that change was not reflected in Port. If we can't get updates for all these actions it would be nice to set a regular schedule to refresh the data and fill the gaps.

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.

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

Enhance the Azure integration to fetch powerState of virtual machines. The current API response does not include this data

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.

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.

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

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.

We'd like to be able to Install a Port Teams Bot to our Microsoft 365 environment such that the bot can be authorised to communicate with members and channels in selected Teams Teams. This could then be used as the backend in Self Service Actions to deliver messages to Teams or Users. For example the recent Announcement feature could be connected to this proposed bot meaning the setup time to use that feature would be measured in minutes. Currently we've got to consider building our own backend service to handle the event from Port and figure out how to deliver into Teams. NOTE: Microsoft are end of life'ing the simpler WebHook method of posting to channels and pushing people towards building Bots and PowerActions... Not an ideal approach from a starting from zero context. The vendor DX has produced their own Teams Bot to facilitate messaging users in Teams. As the customer configuring that capability it was very simple and straight forward. I think Port could build a bridge here too!

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.