Project

General

Profile

Actions

Feature #1484

open
CD

Decommission Business Manager project permanently across all environments

Feature #1484: Decommission Business Manager project permanently across all environments

Added by Client Dashboard 11 days ago.

Status:
Submitted
Priority:
Normal
Assignee:
-
Start date:
07/24/2026
Due date:
% Done:

0%

Estimated time:
spec_ref:

conversation:101

build_status:
build_number:
ci_run_url:
scan_status:
scan_report_url:
deploy_status:
preprod_url:
deployed_at:
branch:
pr_url:
security_key:
severity:
paused:

Description

### Problem
The client has requested the **permanent retirement** of the Business Manager project. The project must be **fully removed** from all systems, with no traces remaining in any environment or tool. This includes:

- **Complete shutdown** of all environments (development, staging, production).
- **Permanent deletion** of all data (user profiles, audit logs, financial records) with **no backup or recovery option**.
- **Removal from all tools** (Harbor, Pipeliner, Redmine, etc.) to ensure the project no longer appears in lists, dashboards, or reports.
- **No user communication**—closure will be handled internally without notice.

### Context
The Business Manager project is a secure financial management tool with the following key components:
- **Web App (Next.js)**: Handles user sign-in (Google OAuth) and displays data.
- **API (Go)**: Enforces security, manages data, and logs all actions (stateless, token-based).
- **Database (Postgres)**: Stores user profiles, audit logs, and financial data.
- **Security Model**: Access is restricted via Google OAuth, an email allowlist, and role-based permissions.

The project is currently deployed across multiple environments, and all data must be **irreversibly deleted** to comply with the client’s request.

### Proposed Behaviour
1. **Shut down all environments** (development, staging, production) and disable access to the application.
2. **Delete all data permanently** from the database, including:
- User profiles (name, email, role).
- Audit logs (login events, user provisioning).
- Financial records (if any exist).
3. **Remove the project from all tools** (Harbor, Pipeliner, Redmine, etc.) to ensure it no longer appears in any system.
4. **Verify no traces remain**—confirm the project is inaccessible and untraceable in all environments and tools.
5. **No user communication**—closure will be handled internally without notifying users.

## Acceptance criteria
['- [ ] All environments (development, staging, production) are shut down and inaccessible to users.', '- [ ] All data (user profiles, audit logs, financial records) is permanently deleted from the database with no backup or recovery option.', '- [ ] The project is removed from all tools (Harbor, Pipeliner, Redmine, etc.) and no longer appears in any lists, dashboards, or reports.', '- [ ] No traces of the project remain in any system (e.g., no residual files, logs, or configurations).', '- [ ] The API and web app are disabled, and no requests can be processed.', '- [ ] No user communication is sent regarding the closure.']

## Classification
- feature

## Complexity
- 8/10 — The complexity is high due to the irreversible nature of data deletion and the need to ensure complete removal across multiple environments and tools.

No data to display

Actions

Also available in: PDF Atom