Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Filebrowser: Recycle Bin

Open
#156 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
aws, typescript
Domain
backend, cloud

Research direction

Start by locating the Filebrowser entry point and the existing storage deletion flow; the issue names no files or tests. Compare the implementation with the versioning, trash-record, retention, lifecycle, and purge requirements, and consider the work done only when restore, permanent deletion, retention, and monitoring behavior are defined and covered.

Written by the indexing model from the issue text.

Description

priority/low

Add a central management spot for restoring or finally deleting files and folders.

Recommended setup

  1. Enable bucket versioning on the storage bucket.

  2. On delete, create an app-level trash record and optionally a delete marker by deleting the current version.

  3. Keep noncurrent versions for a fixed retention window with lifecycle rules.

  4. Optionally move older trash data to cheaper storage classes before final purge, if restore speed requirements allow it.

  5. Periodically purge expired trash and monitor noncurrent-version bytes with Storage Lens.

When this becomes expensive

It gets costly when your objects are large, deletions are frequent, and retention is long. It also gets expensive when users repeatedly overwrite the same keys, because every overwrite creates another billable version unless you expire old ones. If you replicate versions for disaster recovery, multiply that storage footprint across regions.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
22h 6m
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/cockpit

All issues in stackabletech/cockpit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.