Feature ideas

Currently whenever scorecard result changes for entity there is no change written to the audit log, making it hard to write automations that triggers on scorecard level change. the current workaround i found is to trigger by audit's .scorecards but this only gets populated when a change in the current entity props affected the scorecard result

When configuring an integration, currently when setting things like PAT tokens or usernames, the integration will create a port secret by default (based on the integration name). At times, I should be able to re-use secrets where an PAT token or username/pass may be shared. Additionally, when setting up and integration, I should be able to set the name of the secret.

The pipeline-run kind should be able to infer branch data directly from the pipeline run's built-in metadata (e.g. sourceBranch or equivalent fields available in the Azure DevOps Pipelines API response) without requiring an explicit Branch parameter to be defined in the pipeline YAML.

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.

We would like to be able to edit action runs with service accounts, without the need to make them Admins.

Now Ocean integrations can run with service accounts, but they still require Admin role. We need the ability to scope the permissions for the ocean integration service account to read/register/update/delete only certain blueprints.

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?

For mature, established git repositories, getting port.yml changes to main can be a challenge. There needs to be a way for developers to preview their port.yml changes in the Port.io Non-Prod organization by having it look for port.yml changes in a lower branch such as feature/port-gitops. This allows them to preview changes without going through a PR process. I currently have this working with GitHub Ocean (ADO currently does not support branches in the same way). But there are quirks to the process. Requires separate mappings for dev and prod (more tooling with Pulumi) Dev mappings require defining the mappings for the default branch first, followed by the override mappings with a configured and maintained list of repos and the feature/port-gitops. The duality causes the main branch changes to update and then the preview branch to update again. Next sync the same cycle happens over and over again. Instead, if the lower branch exists, it should ignore main. I cannot just set the global branch in the dev org because that requires persisted branches in repos which will not fly. kind: file port: entity: mappings: blueprint: '"environment"' icon: if .this.icon then .this.icon else "Environment" end identifier: .this.identifier properties: description: . this.properties .description platform_id: . this.properties .platform_id relations: {} team: if . this.team then . this.team else [] end title: .this.title itemsToParse: .content | if type == "array" then . else [.] end | map(select(.blueprint == "environment")) itemsToParseName: this selector: files: - path: port.yml query: 'true' Followed by a copy with this added. selector: files: - path: port.yml repos: - branch: feature/port-gitops name: poc-port-ocean - branch: feature/port-gitops name: platform-identity

GitHub Ocean allows specifying a default mapping with no repo or branch definition and also a repo/branch level override for file kind in GitOps mappings. I use this in my Port.io development organization to allow developers to preview changes in a lower level branch.

We would like to enforce a signup page for first time users to be required to some data for onboarding the user to our system.