proxmox/docs/archive/00-meta-pruned/FURTHER_REDUCTION_PLAN.md

Further Script Reduction Plan

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

---

Date: 2026-01-22
Current: 760 active scripts
Target: 460-560 scripts (25-40% reduction)
Status: 🟢 Analysis Complete, Ready for Implementation

---

Executive Summary

Yes, the 760 scripts can be significantly reduced!

Through consolidation, framework creation, and merging, we can reduce by 200-300 scripts (25-40%), bringing the total to 460-560 scripts.

---

Reduction Strategy

1. Create Unified Frameworks (High Impact)

Instead of many individual scripts, create parameterized frameworks:

A. Verification Framework

Current: 100+ check/verify/validate scripts
Solution: verify-all.sh [component] [type]
Reduction: 60-80% (80-100 scripts → 10-20 scripts)

B. Listing Framework

Current: 50+ list/show/get scripts
Solution: list.sh [type] [filter]
Reduction: 70-90% (50 scripts → 5-15 scripts)

C. Fix Framework

Current: 100+ fix-*.sh scripts
Solution: fix-all.sh [issue-type] [component]
Reduction: 50-70% (100 scripts → 30-50 scripts)

D. Configuration Framework

Current: 80+ configure/config scripts
Solution: configure.sh [component] [action]
Reduction: 50-70% (80 scripts → 24-40 scripts)

E. Deployment Framework

Current: 100+ deploy/setup/install scripts
Solution: deploy.sh [component] [options]
Reduction: 40-60% (100 scripts → 40-60 scripts)

---

2. Merge Small Scripts

Current: ~150 scripts < 50 lines
Solution: Merge into utility scripts or shared modules
Reduction: 30-50% (150 scripts → 75-105 scripts)

---

3. Consolidate Duplicates

Current: Multiple scripts doing similar things
Solution: Keep best version, archive others
Reduction: 10-20% (50-100 scripts)

---

Implementation Phases

Phase 1: Framework Creation (Week 1)

1. Create verify-all.sh framework
2. Create list.sh framework
3. Create fix-all.sh framework
4. Create configure.sh framework
5. Create deploy.sh framework

Phase 2: Migration (Week 2)

1. Migrate check/verify scripts to verify-all.sh
2. Migrate list/show scripts to list.sh
3. Migrate fix scripts to fix-all.sh
4. Migrate config scripts to configure.sh
5. Migrate deploy scripts to deploy.sh

Phase 3: Small Script Merging (Week 3)

1. Group small scripts by functionality
2. Merge into utility scripts
3. Create shared function libraries
4. Archive originals

Phase 4: Final Cleanup (Week 4)

1. Remove obsolete scripts
2. Consolidate remaining duplicates
3. Update all references
4. Final verification

---

Expected Results

Before:

• 760 active scripts
• Many duplicates
• Inconsistent patterns
• Hard to maintain

After:

• 460-560 scripts (25-40% reduction)
• Unified frameworks
• Consistent patterns
• Easier maintenance
• Better documentation

---

Benefits

1. Maintainability - 25-40% fewer scripts to maintain
2. Consistency - Unified interfaces and patterns
3. Documentation - Clearer structure, easier to document
4. Development - Reusable frameworks, faster development
5. Onboarding - Easier for new developers to understand

---

Risk Mitigation

1. Backup First - Archive all scripts before consolidation
2. Gradual Migration - Migrate in phases, test thoroughly
3. Preserve Functionality - Ensure all features still work
4. Update References - Update all documentation and references
5. Version Control - Use git to track changes

---

Next Steps

1. ✅ Analysis Complete - Reduction potential identified
2. ⏳ Framework Design - Design unified frameworks
3. ⏳ Implementation - Create framework scripts
4. ⏳ Migration - Migrate existing scripts
5. ⏳ Testing - Verify all functionality works
6. ⏳ Cleanup - Archive consolidated scripts

---

Status: ✅ Analysis complete, ready to begin framework creation