Feature ideas

Extend markdown property support to handle non-UTF-8 encodings and invalid Unicode characters. Markdown content may originate from various sources and tools and is not always guaranteed to be clean UTF-8. Failing hard on a single invalid character makes markdown properties fragile and can block ingestion for otherwise valid entities.

Currently, you cannot delete any custom logos you've imported. It would be useful to have an API endpoint to remove unwanted custom logos. At least, uploading a logo with the same name as an existing logo should override it, so even without deletion, you can replace unwanted custom logos.

We are going about cataloguing a list of entities (type doesn't matter). These have to be manually discovered in our company and then we add a entity.json to the repo's so they get harvested and ingested into Port. Given the distributed nature of the repos this can take some time. We'd like to first "manually" register these entities in port and then over time sync them to their entity.json metadata as those are merged into various repos. You can see the source of a entity by looking at the audit log screen but I can't surface this on the catalogue table view. So I can't tell which ones are just manually still waiting to be linked to a entity.json etc. Could we have a new column that pulls the most recent audit log change for the entity source. So "API" etc or "Manual"

It could happen that the aggregation property cannot be made because of the limitation on the number of entities to aggregate. I would like to be able to go further with this limitation. It could be made with some drawbacks such as a worse freshness in the calculation (example: 1 minute if less than 500 entities, 10 minutes for less than 5000, ...)

Add the ability to mirror a property from a related blueprint even, regardless of the direction of the relation.

Improve export/import reliability, environment promotion, and multi-org migration to prevent rollout delays and support enterprise adoption. especially the native terraform tooling

When you define a relation mapping, entity ingestion will fail when the relation doesn't exist. There is a "createMissingRelatedEntities" flag that when set to true will create dummy entities so ingestion can succeed but you don't always want these dummy entities. There should be a flag like "ignoreMissingRelations" that when set to true would first try to map the relations but would still ingest the entity even if the relation doesn't exist.

Introduce admin-defined tags/badges (e.g., “Managed by Terraform”) on blueprints/actions to improve governance and reduce ClickOps drift.

At this time, we do not have the ability to have more than 100 related entities. I would like to be able to increase this number for our needs.

I want to be able to remove an existing condition. Today, the only workaround is adding an empty object in order to clear the conditions, which is not intuitive.