Feature ideas

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"]

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

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.

Instead of requiring a change to the port.yml it would be great if we could resync the GitOps data source.

Currently, you can update the integration mapping config and default blueprints through the ocean integration after deploying. Adding the option to provide those as parameters in the helm chart could make the process of deploying integrations faster and better.

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

Add a functionality for batch deleting/updating/creating entities

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.

Currently, Port lacks a command-line interface (CLI) tool for creating blueprints, entities, scorecards, and other functionalities. Introducing such a tool could provide valuable assistance to users.

Today you can manage permissions on a Page, Self service, and blueprint level. Since some IDPs can have multiple "Builder" teams in different business domains, it would be ideal to have the option to define for each data source who has permissions to view the mapping, and modify it.