Skip to content

Consolidate storage cleanup patterns into 'Delete or auto-expire unused storage' - #438

Open
russelltrow wants to merge 1 commit into
mainfrom
consolidate-storage-cleanup
Open

russelltrow wants to merge 1 commit into
mainfrom
consolidate-storage-cleanup

Conversation

@russelltrow

Copy link
Copy Markdown
Member

Title

Delete or auto-expire unused storage

Version

1.0

Submitted By

greenhsu123 (original author of both source patterns)

Published Date

2022-11-10 (carried over from the originals; to be confirmed by the patterns working group)

Intent

Reduce the storage hardware needed by deleting unused storage, manually or via retention policies, without losing data that is still needed.

Tags

storage, data-lifecycle, size:small

Problem

delete-unused-storage-resources (manual) and set-retention-policy-on-storage-resources (automated) share an author and date and have word-for-word identical Assumptions. Both fail principles 5, 8, 10 and 11 in the August 2026 Operations analysis. Only the manual one mentioned data-loss risk, even though automated deletion is arguably riskier.

Solution

One pattern with two techniques (manual deletion; retention-policy expiry) and a shared set of safeguards: named owners and retention periods, review before manual deletion, soft-delete or grace periods, and testing new policies on non-critical data first.

SCI Impact

SCI = (E * I) + M per R

M decreases (fewer storage devices needed); E is lower only marginally.

Assumptions

Unused storage can be identified; each data class has an owner who can state retention needs; legal/regulatory retention is documented first; the platform supports deletion rules or soft-delete if automating.

Pros & Cons

  • PRO: Removes duplicate content; data-loss risk now covered for both techniques; testable Assumptions; adds Cost Impact.
  • CON: Two URLs retire (redirected). Cost Impact is qualitative, with no quantified figures.

What changed

  • Added docs/operations/resource-lifecycle/delete-or-auto-expire-unused-storage.md (title is the wiki's example wording)
  • Moved the two originals to archive/operations/resource-lifecycle/ (same approach as Archive low quality patterns #426)
  • docusaurus.config.js: old URLs redirect to the new page
  • src/data/personas.ts: old rows replaced with one in the DevOps, Data Engineer and Software Engineer lists (edited by hand to avoid unrelated regeneration drift)

For reviewers

Part of #434.

🤖 Generated with Claude Code

…ed storage'

Merges delete-unused-storage-resources and
set-retention-policy-on-storage-resources (same author/date, identical
Assumptions) into one pattern covering manual deletion and retention
policies, with a prominent data-loss safeguard section and a new Cost
Impact section. Originals moved to archive; redirects and persona data
updated.

Part of #434 (see #385).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@russelltrow

Copy link
Copy Markdown
Member Author

@franziska-warncke I've done another of the really simple Operations patterns consolidation tasks, ready for your review

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant