Feature ideas

We'd like to have the following fields populated by the github-ocean-pr integration for Pull Requests: lines_added, lines_deleted, files_changed, commit_count, reviewers (approved, changes requested by, commented by with timestamps), ci_status (checks API).

Datadog has a very robust and complex RBAC we are using to ensure that users only see what is relevant to them. We want to have Datadog continue to be the source of truth for this and import the RBAC to have Port users only be able to see the data they see in Datadog and nothing more.

ADO has a very robust and complex RBAC we are using to ensure that users only see what is relevant to them. We want to have ADO continue to be the source of truth for this and import the RBAC to have Port users only be able to see the data they see in ADO and nothing more.

The Port Execution Agent currently offers limited insight into its runtime version and the API requests it makes to Port (polling, status reporting, log pushing), which hinders troubleshooting, auditing, and version management in production environments.

Please include AWS::Bedrock::Agent and AWS::BedrockAgentCore::Runtime as supported kinds in the aws v3 integration

AWS v3 Integration – Cloud Control API Fallback for Unsupported Resources Request for the AWS v3 integration to support fallback ingestion through the AWS Cloud Control API for resources that do not yet have dedicated resource-specific API support. Today, the older on-prem AWS integration can cover a much broader set of AWS resources through Cloud Control API, while the newer v3 integration provides richer and more modern metadata but supports fewer resource types. This creates operational friction where customers must run both integrations in parallel to achieve full AWS coverage. A Cloud Control API fallback mechanism would allow v3 to ingest unsupported resources automatically, reducing gaps in coverage, minimizing maintenance overhead, and avoiding the need to add AWS resources one-by-one over time.

AWS Integration – Support for AgentCore and Bedrock As customers expand their AI and agent ecosystems, Port’s AWS integration should support AWS AgentCore and Amazon Bedrock as first-class resources/services. This would allow platform teams to catalog, visualize, govern, and automate AI agents, models, prompts, and AI workflows directly within Port. Key use cases include: Tracking ownership and lifecycle of Bedrock models and AI applications Surfacing AgentCore agents/services in the software catalog Enabling self-service actions and workflows around AI infrastructure Creating governance, scorecards, and visibility for enterprise AI adoption This would significantly strengthen Port’s position as the central control plane for platform engineering and AI operations.

Add support for reliably identifying the earliest commit & timestamp that belongs to a "Deployment" across GitHub, GitLab, and Azure DevOps, as this is required to calculate Lead Time for Changes regarding DORA metrics.

To extend support for additional AWS resource types in the Port-hosted AWS integration, for DynamoDB Tables, Secrets Manager Secrets, Backup Vaults, Route53 Hosted Zones, VPCs, and Subnets. These resources are currently only available via the self-hosted AWS exporter. Adding support for them in AWS port hosted would be beneficial.