Feature ideas

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.

We want to add support for installing the skills from port CLI in VSCode It supports the same hooks as Cursor which you already support so I think this should not be a big effort.

The native GitLab integration in Port does not currently expose the duration field for pipeline entities. We'd like this field to be supported natively. The current pipeline kind mapping fetches data from the GitLab list pipelines endpoint (/api/v4/projects/:id/pipelines), which returns fields such as status , created_at , updated_at , and web_url . However, the duration field is only available on the individual pipeline detail endpoint ( /api/v4/projects/:id/pipelines/:pipeline_id ). What we need: For each pipeline fetched during resync, we'd like Port to also retrieve the detailed pipeline record so that the duration field is available for mapping.

Add support for ingesting billing and cost usage data, including consumption, credits, usage-based charges, and gross/net cost by user, org, account, and model. This would help customers monitor spend, understand consumption patterns, and measure cost efficiency.

Current Behavior: When a Port integration is deleted, its associated secrets stored under Credentials → Secrets are not automatically removed. These stale secrets persist and can cause a "secret already exists" error if a user attempts to recreate the same integration type later. Desired Behavior: When an integration is deleted, Port should either: > Automatically delete all secrets associated with that integration, or > Display a prompt/warning during the deletion flow reminding users to manually clean up the associated secrets to avoid conflicts on re-creation.

Summary Track PR Rework as a key engineering metric - the number of review cycles or post-review commits before a PR is approved. Integrations Should support the following key SCMs: GitHub GitLab Azure DevOps

Can Port support ingesting AWS costs from the Cost explorer API? https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/Welcome.html There is an official aws plugin for backstage that does this https://github.com/awslabs/backstage-plugins-for-aws/tree/main/plugins/cost-insights The link provided here is no longer valid. https://roadmap.getport.io/ideas/p/aws-exporter-support-cloud-resources-costs

Add a native Port integration with Harness to sync cost and deployment data into the Port catalog. Key capabilities needed: > Pull cost data (ideally at resource/ARN level) into Port entities > Enable cost attribution by service and team ownership > Surface Harness cost visibility alongside other catalog data without requiring expert-level Harness dashboard access This would allow platform teams to tie cloud spend directly to service owners in Port, driving cost accountability without requiring developers to navigate Harness directly.

The Snyk Target portion of the port hosted Snyk integration is not returning empty targets (targets with no projects). The default behaviour of the Snyk api appends the exclude_empty=true query param to the next page link. I'd like there to be a way to tell the integration not to exclude_empty targets. We want a way to be able to see if a repo is in Snyk or not, but we have repos in snyk that don't have projects. Maybe it can be an additional selector?

Currently the ADO kind for Test Runs containers both Code Coverage and Test Results. These should be separate kinds.