Feature ideas

currently, this tag is set to true automatically and there is no way to turn it off. Having these configurable may solve some problems when ingesting via webhook

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.

Today when a request is to made to Port's API using a standard API call (meaning, not with an integration), the Port user info in Port just shows Rest API. As customer usage of Port increases, they are likely to have more than a single backend that makes requests to Port API to send information, and it would be helpful to tag the source of each of those requests so that they appear in the audit log in a clear manner. An alternative could be multiple Client ID and Secret pairs, which each can be tagged as a specific "app" with it's own label in the Port user info column

Add a functionality for batch deleting/updating/creating entities

Currently, self-hosted Ocean integrations require organizational credentials. Ideally, service account credentials should be used to improve security and create different tokens for different integrations.

Currently, when you want to deploy a new self-hosted integration, the organization's client ID and client secret are used by default. So, if the client ID and client secret are leaked or need to be changed, you must change the client ID and client secret for all integrations that you host yourself A better way would be to generate a new service account for a new integration, so you have only one key to manage per integration This is in line with the principle of least privilege and allows for easy, secure management of dedicated service accounts

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

Today it is only possible to integrate using basic auth, and this feautre request is about being able to authenticate to SNOW using OAuth

Problem Statement: In some environments, the Port Agent must communicate with services secured by non-standard or private certificate authorities. Currently, there is no straightforward way to mount custom CA certificates into the agent container when deployed via the Helm chart. This limitation makes it difficult to operate in environments with custom security requirements. Proposed Solution: Extend the Port Agent Helm chart to allow users to specify additional volumes and volume mounts. Provide an example configuration to demonstrate mounting a secret or ConfigMap containing custom CA certificates. Ensure the agent container recognizes and utilizes the mounted certificates for outbound communication. Benefits Enables secure communication with services protected by private or non-standard CAs. Improves flexibility of Port Agent deployments in enterprise and regulated environments. Reduces the need for manual workarounds or custom image builds. Example Values.yaml with extra volumes extraVolumes: - name: custom-certs secret: secretName: custom-ca-secret extraVolumeMounts: - name: custom-certs mountPath: /etc/ssl/certs/custom readOnly: true

On startup, log the active mapping hash and the exact blueprint targets (e.g., targets=[cluster,namespace,node,workload,replicaSet,pod,gateways,virtualServices]). This will make configuration drift or unintended merges immediately visible.