Feature ideas

Incident.io is an incident management tool gaining in popularity. It would be great to get a pre-built integration to make transition to Port easier for companies that are already using incident.io

Current Behavior When the GitLab integration fails or gets restarted, all webhooks are failing. After a few retries, these webhooks are marked as failed and disabled, potentially for up to 24 hours. This behavior is documented in the GitLab webhook documentation: https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#temporarily-disabled-webhooks Desired Behavior The integration should handle scenarios where webhooks fail due to integration issues or restarts. As part of the existing resync process, the integration should automatically test and enable the configured webhooks to ensure continued functionality. Proposed Solution Enhance the existing resync mechanism in the GitLab integration: Add a new step in the resync process to handle webhook validation and enabling. For each configured webhook, send a test request to the webhook using the GitLab API. (Reference: https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#test-a-webhook ) Benefits Improved reliability of the GitLab integration. Reduced downtime for webhook-dependent processes - consistently working real time updates. Decreased manual intervention required to maintain webhook functionality. Seamless integration with the existing resync process.

Ingest cloud vulnerabilities from Orca

Currently I understand that the k8s exporter only support polling the kube api for resource changes and so the data in Port can end up being out of date and stale. Could the exporter instead watch resource in k8s and therefore achieve near Realtime updates in Port. This would unlock many use cases where the architecture of the "Platform" using Kubernetes as the "API" and Port as the front-end portal to the Platform services and data.

Currently, Terraform provider does not allow managing permissions of blueprints and actions. It would be great to manage everything in one tool - blueprints, entities, actions, as well as its RBAC

The terraform provider needs data types to allow for terraform users to query port.