Custom retention for blueprint entities
Mor Paz - Port team
Some data models include blueprints such as CI/CD jobs or deployments. These blueprints usually get filled with high number of entities, but the entities in these blueprints become stale and lose relevancy very quickly.
With this feature, users will be able to configure custom retention for specific blueprints, giving them the option to automatically delete old entities once the number of entities for the blueprint passes X entities, or if an entity was updated more than 1 week/month/year ago
Activity Feed
Sort by
Gur Shafriri
This can now be done with Automation:
- when creating an entity, also add a TTL timer field set to the retention timeframe.
- Create an automation that will delete this entity when TTL expired
Dipak Parmar and others Let me know what you think
G
Glenn Moen
Gur Shafriri This seems like a work around for the feature request. Was that the intention? For my use cases, it would be better to set this at the blueprint level instead of the entity level. If I want to add retention to an existing entity, it would require updating all entities. If I decided to change a retention period, it would require updating all entities.
Gur Shafriri
Glenn Moen yes 100% a workaround - it would be ideal to have it as a built in blueprint feature.
I also didn't consider bulk changes as you mentioned - these can also be done with automation/migration but I see how it can become complex.
Anyway, I wanted to share a way to currently do this until this get's prioritized as a feature in case it helps someone.
G
Glenn Moen
Gur Shafriri Thanks for the response and clarification.
Dipak Parmar
+1 for this, we have excessive of amounts jobs that runs and we need them in port, but after certain days they are not useful, clutters the system. we can keep the in cicd system, not necessary we need them in port, aggregate is okay.