GitHub user mistercrunch added a comment to the discussion: cannot delete user "Associated data exists, please delete them first"
Right. Deleted flag + optional/configurable reassignment sound right. At Preset we rewire logs elsewhere, but could see many options as to how to treat deletion being valid for different use cases. For instance GDPR probably requires deleting or obfuscating PII and log events. Seems we need an endpoint that can provide all this, and maybe policies/configuration around it. Trying to list out options: - soft delete, keep user info - soft delete, obfuscate PII - true delete, also delete logs This in combination with reassignment options: - reassign object ownership to a single user - delete owned objects (seems dangerous) - orphan owned object, might create issue where ownership is required (?) I'm probably overthinking all this. Might be able to support 95%+ of things a few option combinations GitHub link: https://github.com/apache/superset/discussions/40137#discussioncomment-16924839 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
