Feature ideas

https://support.pagerduty.com/main/docs/custom-fields-on-services We have Custom Fields on Pagerduty Services that let us correlate back to the Gitlab project and the Owning team. It would be wonderful if the Pagerduty integration could pull those in so we could setup the relationships properly.

Currently, SSO integration only populates the email field in _user. Some integrations, such as GitHub, require mapping additional identifiers that are not currently provided via SSO. To support these cases, we need the ability to store extra attributes from identity providers in _user. Benefit: Enables seamless mapping between SSO-provisioned users and external systems that require unique identifiers beyond email.

Currently, Ocean metrics webhooks only support passing a webhook URL, adding support for webhook secrets to enhance the security of metrics data sent from Ocean integrations to monitoring endpoints

For easier integration with Prometheus

We prefer to deploy through certified marketplace listings for easier deployment and compliance.

Some integrations have Kinds that have fast changing data and other Kinds have slow changing data. I want to control the refresh interval individually so that some Kinds are refreshed more often than others. What we find is that some of the Kinds with large counts can slow down the refresh. Fixing this could be achieve by allowing an interval setting by Kind or by allowing multiple instance of the same Ocean integration or by allowing asynchronous loading of Kinds

Today when mapping GitHub Users and Github teams, they are mapped separately and cannot be related (can't see which teams a GitHub user is under.) This is something that is logically expected as they are related entities in GitHub itself

Today a delete operation of the file is not deleting the mapped entities from Port in the file kind of Git integrations

As a FinOps team member, I want to ingest data from FinOut to deliver it to developers. Right now, I struggle to deliver FinOps optimization advice to them and doing so in Port is the ideal way.

Currently, it's not possible to bring in certain fields from Github via the Cloud Github Port App as it requires WRITE permissions. For example, whether a repo has code scanning or secret scanning enabled is not available currently as Port's Github App does not have write permissions. { "security_and_analysis": { "advanced_security": { "status": "enabled" }, "secret_scanning": { "status": "enabled" }, "secret_scanning_push_protection": { "status": "disabled" }, "secret_scanning_non_provider_patterns": { "status": "disabled" } } } Giving customers the ability to toggle on/off WRITE permissions for their Github Port Cloud App to ingest this data would be useful as currently it's only possible to bring it in via the self-hosted Github App.