"Lock" critical entities to prevent accidental deletion
T
Thomas Felix
In order to prevent an accidental deletion e.g. of a Platform Instance (which also removes all tenants from meshStack for this platform) via the panel or external API. I want to have some sort of flag which can be set via the panel or meshObject API which then prevents any deletion operation. Only if this flag is manually updated before, the deletion is possible again.
Janny the AI Product Manager
Thanks for taking the time to share this — the “lock” flag idea to prevent accidental deletion of critical entities (like Platform Instances) makes a lot of sense, especially given the blast radius when tenants get removed as well.
A couple quick questions so we can pass this on with the right context:
1) Which entity types would you want to be lockable beyond Platform Instances (e.g., Platforms, Projects, Tenants, Landing Zones)?
2) Should the lock block deletions from both the panel and all APIs (including automation), or are there cases where an API delete should still be allowed?
3) Who should be allowed to toggle the lock/unlock (e.g., only specific admin roles), and would you want an “override” flow like an extra confirmation step?
We’ll share this with the team — if you have an example of a near-miss or a specific workflow where this would have helped, that’d be great context too.