[Feature Request] - Delete persistent profile data when a user is deleted

[Tetrachloromethane250]

Existing Resources

• Please search the existing issues for related items
• Consult the product documentation : Docs
• Consult the FAQ : FAQ
• Consult the Troubleshooting Guide : Guide
• Reviewed existing training videos: Youtube

Is your feature request related to a problem? Please describe.
In my use case a group of users are created every month or two, use a workspace with a (S3 based) persistent profile for ~1 week, then are deleted.
This leaves behind their persistent profile data in S3, which then needs to be manually deleted.

Describe the solution you'd like
When a user is deleted in Kasm, their persistent profile data should also be removed.

Describe alternatives you've considered
Semi-regular manual clean up
S3 lifecycle rules (fails on deleted user vs infrequently used user)

Additional context
Most use cases probably don't delete users as frequently as I do, however the data would still be left behind (just at a slower rate)
Docs suggest using {username} or {user_id} in the persistent profile path, not clear how easy it is to go from a user to a list of their persistent profiles across potential multiple workspaces.
It's possible this may already be included in/planned as part of the new Storage Mapping based profiles. It is not mentioned in the docs, and as it is described as not production ready I haven't configured it.

[teja-kasm]

Hi, thanks for the suggestion.

I can confirm that currently we do not have a feature that deletes a user's S3 profile when the user is removed from Kasm (not even in the new, experimental Kasm Profile Sync storage provider feature).

This is a nice feature to have and I will push internally. However, I can't guarantee when/if this feature will be planned. I will update here when I have some more information.

[teja-kasm]

Thanks for the suggestion - an internal feature request has now been created to track this (Internal Ticket reference: KASM-8022).

At this time, we don’t have a timeline for when this might be implemented, or whether it will be included in a future release. If there are any updates or movement on the request, I’ll follow up here.