Feature ideas

Add a resync button to the k8s exporter which will trigger a resync exactly as it appears in other integrations. You can see the button in the screenshot

Problem Statement Currently, port.io requires API write access and organization owner permissions to automatically configure webhooks in gitlab. This violates security best practices by granting excessive privileges across the entire organization. While a temporary workaround (using a personal access token with owner rights) has been implemented, it's unsustainable and creates unnecessary security risks. Proposed Solution Enable customers to manually configure webhooks by providing the generated ingest.ocean.getport.io/live-events url plus the secret needed to send the events.

Hosted by Port ocean integrations can hit out of memory errors at high scale because all integrations get the same fixed resources today. When that happens, customers experience instability in heavier integrations. We would like to add an autoscaling mechanism that will recognize when an integration gets to the limit of its resources and automatically scale the resources to support high scale of data.

When visiting a specific page in Port I would like to automatically trigger the (re)sync of a specific data source. Currently my option is to manually resync it from the Builder page, or start a Self service action to trigger it.

Currently, the API data source card displays all blueprints that have ever been successfully ingested through them. Even if the entities ingested via API for those blueprints are removed, those blueprints continue to appear in the data source card. This can cause confusion and unnecessary clutter, as the card no longer reflects the active mappings.

Currently: Data extraction configuration such as selecting which kinds to extract and defining API level selectors is set in the mapping. This means that the first sync after installing the integration includes only the default kinds and no selectors. The extraction behavior changes only after a user updates the mapping. Expected: We would like to move all configuration related to the extraction phase from the mapping to the installation and settings pages. This would allow users to filter data and choose kinds from the API even during the initial installation. It would also improve discoverability of available kinds and filters. This change is also required for the new architecture of the upcoming mapping experience planned for Q1.

Currently, the mapping modal, shows only kinds and examples that are mapped in the mapping yaml. Customer can't know which other kinds are available without looking in the docs. We would like to add to the kinds examples all kinds that are supported in the integration, even if they aren't mapped by default/ by a customer

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.

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

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