delete-user

Name: delete-user
Availability: InStock
Author: Systemorph

Drop PostgreSQL schemas for deleted users and restart portal deployments in AKS environments.

11|4|Updated Jan 15, 2024

Search Tags:#postgresql #kubernetes #cleanup #administration #user-management #meshweaver

Ready to run

npx skills add https://github.com/Systemorph/MeshWeaver --skill delete-user-systemorph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delete-user
Source: https://github.com/Systemorph/MeshWeaver/tree/main/.claude/skills/delete-user
Command: npx skills add https://github.com/Systemorph/MeshWeaver --skill delete-user-systemorph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the issue where standard API calls prevent the deletion of user partition roots, allowing administrators to cleanly remove test accounts or reset user data that would otherwise persist in the system.

Core Features & Use Cases

Postgres Schema Management: Safely identifies and drops user-specific database schemas associated with both user IDs and email addresses.
In-Memory Cleanup: Orchestrates portal restarts to ensure that cached user nodes are fully purged and cannot be resurrected by the system.
Use Case: Use this when you need to fully decommission a throwaway test user or reset a user who has encountered a corrupted onboarding state, ensuring no residual data remains in the Postgres backend or the portal memory.

Quick Start

Execute the delete-user skill by providing the unique identifier fragment of the user you wish to remove from the system.

Frequently Asked Questions about delete-user

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I delete a user partition when standard API requests fail to remove it?▼

To delete a protected user partition, you must drop the associated Postgres schemas and trigger a portal deployment restart. This bypasses standard API restrictions to directly remove user-specific data footprints from the backend and clear cached in-memory nodes.

Why does a deleted user still appear in the portal after removing their data?▼

A deleted user may reappear in the portal because cached user nodes remain in memory. Orchestrating a portal deployment restart purges these cached nodes, ensuring the user cannot be resurrected by the system after their database schema is dropped.

What's the best way to clean up test user data in a production AKS environment?▼

The best way to clean up test user data in production AKS is to execute SQL commands against the internal Postgres database to drop user schemas, followed by restarting the portal deployment to purge any residual cached user nodes from the system.

Do I need kubectl access to remove user-specific Postgres schemas from MeshWeaver?▼

Yes, you need kubectl access to the production AKS cluster and the ability to execute SQL commands against the internal Postgres database. These permissions are required to drop user partitions and trigger the necessary portal deployment restarts.

When should I manually drop Postgres schemas to reset a user onboarding state?▼

You should manually drop Postgres schemas when a user encounters a corrupted onboarding state or when you need to fully decommission a throwaway test account. This ensures no residual user-specific data remains in the backend database or portal memory.