Feature ideas

It would be good if the slack integration could pull the slack channels so we could create a blueprint for them and use it in self service forms to give users a dropdown list of channels.

Add branches attribute to the project data. This will include all branch data associated with a project, allowing entities to be properly mapped. Additionally, the branch names from analysis could also be included as a relation for better visibility.

I'd like to add to this Kafka ACLs, Kafka Principals, Confluent Schema registries and Confluent Schemas.

Please add support for the Labels field when importing project data from GitLab https://docs.gitlab.com/ee/user/project/labels.html https://docs.gitlab.com/ee/api/labels.html

Some integrations have Kinds that have fast changing data and other Kinds have slow changing data. I want to control the refresh interval individually so that some Kinds are refreshed more often than others. What we find is that some of the Kinds with large counts can slow down the refresh. Fixing this could be achieve by allowing an interval setting by Kind or by allowing multiple instance of the same Ocean integration or by allowing asynchronous loading of Kinds

As a Port admin, I occasionally add entities to Port using the API. Sometimes, I try to add a property that does not (yet) exist, or I misspell a property identifier. Currently, the API allows for the entity to be created, and instead of raising an error about an incorrectly entered or nonexistent property, the entity is allowed to be created and properties which did not receive value specifications from the API call are assigned the default property. This is not ideal: I would like either to have an error raised blocking the entity, or (ideally) have an error raised explaining that I tried to add a value to a property that does not exist.

Currently if you delete a repo in Github, it's not synced in real-time to Port (unless you manually trigger a new sync).

Currently, the GitHub integration can't be set up with multiple instances, which means that only one instance is owning all entities. This becomes problematic when you want to have two kinds populate the same entities. The reason for that, is the query field can result in an entity being deleted from the "enriching kind" rather than the "owning kind". Suggestion: Add to entities created by the GitHub app a new type of ownership, based on the mapping kind. This will allow only specific kinds to delete entities from the catalog, while allowing other kinds to safely "enrich" the entities.

Ingest Azure Devops Pipeline runs Today only pipelines are supported, not run results

The ServiceNow TableAPI integration is great, I can fetch from all sorts of standard and custom tables. The issue is that many of the tables I want often have 10's of thousands of entries and as the integration works slowly through many entities, are unlikely to ever complete a sync. One key example is cmdb_ci_rel which contains key relationships between entities. If the integration could expose some of the filters from the table API through the mapping configuration, that would be incredibly enabling!