Feature ideas

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.

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

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

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.

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.

It would be helpful if we had a trips and tricks section in the Port UI or in our documentation to show that users can always do trips and tricks on their JQ mapping to avoid some user-specific errors. For example, say the user gets the following error in the Audit logs "last_push" must match format "date-time" Then they could solve it by changing the default mapping from last_push: .pushed_at to last_push: .pushed_at | (if type=="number" then todateiso8601 else . end)

Today, when updating new objects / arrays of entities the new value overrides the old one. With this feature it will be possible to append values to these properties. Example of Tags property with type of array: Current state: "Tags" : ["tag1"] Ingesting a new tag using the API: "tag2" New state: "Tags": ["tag1", "tag2"]