delete-module.sh¶
Deletes a TAPPaaS module with dependency-aware service teardown.
Usage¶
Parameters¶
| Parameter | Description | Example |
|---|---|---|
module-name | Name of the module to delete | vaultwarden |
--force | Delete even if other modules depend on this module's services |
What it does¶
- Validates the module JSON config exists in
/home/tappaas/config/ - Checks reverse dependencies — blocks if other modules depend on this module's services (unless
--force) - Calls the module's own
delete.sh(if present) while the VM still exists - Iterates
dependsOnin reverse order and calls each provider'sdelete-service.sh(skips if not found) - Removes the module configuration files (
.jsonand.json.orig)
Examples¶
Notes¶
- The deletion order is reversed compared to installation: the module's own
delete.shruns first (while the VM still exists), then services are torn down in reverse dependency order - HA/replication is removed before the VM is destroyed to prevent conflicts
- Missing
delete-service.shscripts are skipped (not an error), allowing incremental rollout - Service teardown failures produce warnings but do not abort the overall deletion
See Also¶
- install-module.sh - Install a module
- update-module.sh - Update a module
- Module Structure - Detailed module lifecycle documentation