Feature ideas

We use GitLab and GitOps to sync a lot of our data. We pre-map the data to port format already in our files. And then we have to jq-map each individual field and relation in the mappings as well. First, it feels extremely unnecessary, since the files are already in the port format. Second, it creates extra room for error, and extra work - we need to update mappings each time we change the models and files. One way to solve this would probably be allow the "{{ spreadValue() }}" operator in the mappings. Or just a flag to consume entities directly as-is for GitOps integrations.

Enable users to validate integration setup before full installation by testing connectivity, access, and basic permissions. Reduce setup errors and improve user confidence in integration correctness during onboarding.

We need the ability to pause and resume data source syncs. While we understand that rate limits determine the sync frequency, having the option to pause and resume would give us control over the order in which data sources sync. This capability is essential as we gradually roll out Port to different teams, ensuring their service data is accurately captured and reviewed before proceeding to the next team.

We recently deployed a SonarQube integration using the hosted solution. Due to our custom IaC setup, we use non-standard blueprint names, but the integration continues to install blueprints and pages with default names. I attempted to disable this using the initializePortResources: false option in the configuration, but it had no effect. It would be helpful to have an option to completely disable the creation of default resources.

In scenarios where multiple (and growing) numbers of Kubernetes clusters exist in a customer environment, using one exporter per cluster won't be feasible; therefore, it would be important for the K8s exporter to be able to extend to multiple clusters.

Managing data (sending and viewing) in separated blocks (pagination) in audit logs

Currently, there's only one data source, for searching entities. I would like to request that we get _multiple_ terraform data sources for basically all resources, for use with features like terraform checks/validation. As a concrete use case, currently, I have a check that uses the data "http" resource type to: 1) Hit the access token url and get a Bearer token (this could be an ephemeral data source, please) 2) Using that token, hitting the https://api.port.io/v1/blueprints api endpoint to get a list of _all blueprints_, including those not managed in terraform. 3) Using that response, I create a set of all blueprint identifiers both in the current workspace, as well as in my port environment. Then, assert on the difference. If there are any blueprints present that are not managed in port, the check fails the condition, and I use setsubtract to print a list of the blueprints that differ (and thus I need to import into terraform. With some bits removed, this looks like: check "get_all_blueprints_and_compare_with_terraform" { data "http" "port_all_blueprints" { url = "https://api.port.io/v1/blueprints" method = "GET" request_headers = { Accept = "application/json" Authorization = "Bearer ${jsondecode(data.http.port_bearer_token.response_body).accessToken}" } } assert { condition = toset([ for bp in jsondecode(data.http.port_all_blueprints.response_body).blueprints : bp.identifier ]) == local.terraform_blueprint_identifiers error_message = <<-EOT Blueprint identifiers do not match between Port API and Terraform configuration. Only in API: ${join(", ", setsubtract(toset([for bp in jsondecode(data.http.port_all_blueprints.response_body).blueprints : bp.identifier]), local.terraform_blueprint_identifiers))} Only in Terraform: ${join(", ", setsubtract(local.terraform_blueprint_identifiers, toset([for bp in jsondecode(data.http.port_all_blueprints.response_body).blueprints : bp.identifier])))} EOT } } I think this could be much cleaner with a data source coming from port itself (and could be extended to other types as well, like pages).

Add option to specifically resync a predefined list of resources & do a scheduled resync only for a selected list of resources

Example: Someone integrated a k8s cluster integrated to Port with the K8s exporter, but the cluster is deleted. The situation we’re stuck at is that data is stopped from syncing, but we have orphan entities stuck in Port, that will never be deleted because their owner is deleted. Same for disconnected GitHub, Jira etc. expected solution from the product: An ability to delete all entities of a certain data source from Port (when clicking on the ... of a certain integration in the Port UI / via API

A new kind of resource has been added to Github - "Enterprise". An enterprise is one level above an organization, and each enterprise contains multiple organizations. So ideally, we would want to be able to install the GitHub app on an enterprise level rather then on an organization level, and integrate with all organizations under that enterprise. That way, we don't need to install the integration on each organization, but we can just install it once per enterprise, and configure the mapping for all orgs through one enterprise. More info about enteprises can be found here https://github.blog/changelog/2024-10-22-enterprises-can-create-github-apps-for-use-within-the-enterprise/