Tornevall Networks

← Back to docs

IMPLEMENTATION

Language: EN | EN | SV

IRC Log Rollback System - Implementation Summary

What Has Been Implemented

1. Database Schema Changes

Migration: 2026_03_01_000000_add_rollback_tracking_to_batches.php

Added columns to import_batches table:

Added columns to irclog_import_jobs table:

2. Permissions

Migration: 2026_03_01_000001_add_irclog_permissions.php

Created two new permissions:

3. Service Layer

File: app/Services/IrcLog/ImportRollbackService.php

A comprehensive service handling rollback operations:

Methods:

4. Controller

File: app/Http/Controllers/Admin/IrcLog/ImportRollbackController.php

Handles web requests for rollback operations:

Routes:

Middleware: Requires auth:web + can:irclog.manage

5. Views

3 New Blade Templates:

  1. resources/views/admin/irclog/rollback-confirm.blade.php

    • Shows job and batch details
    • Requires reason input (min 10 chars)
    • Confirmation checkbox required
    • Warns about permanent data loss

  2. resources/views/admin/irclog/rollback-history.blade.php

    • Paginated table of all rollbacks
    • Shows: batch ID, source file, when, who, reason
    • Tooltips for detailed reason viewing

  3. Updated: resources/views/admin/irclog/show.blade.php

    • Added "Rollback from Production" button when job is done
    • Shows rollback status if already rolled back
    • Only appears if production_batch_id exists and not yet rolled back

  4. Updated: resources/views/admin/irclog/index.blade.php

    • Added "Rollback History" button to navigation
    • Links to audit trail view

6. Controller Updates

Updated: app/Http/Controllers/Admin/IRCLogImportController.php

Modified approve() method to:

Modified mergeToProduction() method to:

7. Routes

File: routes/web.php

Added 4 new routes in the admin/irclog prefix group:

Route::get('/{job}/rollback', 'ImportRollbackController@confirm')
    ->name('admin.irclog.rollback.confirm');

Route::post('/{job}/rollback', 'ImportRollbackController@execute')
    ->name('admin.irclog.rollback.execute');

Route::get('/rollback/history', 'ImportRollbackController@history')
    ->name('admin.irclog.rollback.history');

Route::get('/api/rollback/{job}', 'ImportRollbackController@info')
    ->name('admin.irclog.rollback.info');

8. Documentation

File: docs/irclog-rollback.md

Comprehensive documentation covering:

Workflow

Complete Approval & Rollback Workflow

Upload Log File
    ↓
Detect Format
    ↓
Run Dry-Run (Sandbox)
    ↓
Review Results
    ↓
[APPROVE] ← User records who approved & when
    ↓
[MERGE TO PRODUCTION] ← Copies approval info to batch
    ↓
✓ DONE (in production)
    ↓
[IF ERROR] → Click "Rollback from Production"
    ↓
Confirm Rollback (provide reason)
    ↓
Delete from Production (recorded with who & why)
    ↓
✓ ROLLED BACK (audit trail preserved)
    ↓
Check "Rollback History" to verify

Usage Example

  1. Approve a job:

    • Click "Mark as Ready for Production" button
    • System records your user ID and current timestamp

  2. Merge to production:

    • Click "Merge to Production" button
    • Approval info is copied to batch record
    • Events are imported to production

  3. Realize mistake:

    • Go back to job detail page
    • Click "Rollback from Production" button (now visible)

  4. Confirm rollback:

    • Review all details
    • Type reason: "Test data imported by mistake"
    • Check confirmation checkbox
    • Click "Execute Rollback"

  5. Verify:

    • See success message with count of deleted events
    • Go to "Rollback History" to see audit trail
    • Job now shows "⚠️ Rolled Back on [date/time]"

Data Integrity Features

✓ Audit Trail: All approvals and rollbacks are permanently recorded ✓ User Tracking: Always know who approved and who rolled back ✓ Reason Tracking: Why decisions were made ✓ Batch Linking: Complete traceability from job to batch to rollback ✓ Timestamp: Exact timing of all operations ✓ Event Count: Know exactly what was deleted

Security Considerations

Testing

To test the system:

# Run migrations
php artisan migrate --path=database/migrations/irclog/2026_03_01_000000_add_rollback_tracking_to_batches.php
php artisan migrate --path=database/migrations/2026_03_01_000001_add_irclog_permissions.php

# Check routes
php artisan route:list --path=admin/irclog | grep rollback

# Test service
php artisan tinker
> $service = app(App\Services\IrcLog\ImportRollbackService::class);
> $result = $service->rollbackJob(1, auth()->user(), 'Testing');
> dd($result);

Files Modified/Created

New Files:

Modified Files:

Next Steps

The system is ready for production use! To enable for users:

  1. Ensure migrations have run
  2. Grant irclog.manage permission to appropriate users
  3. Train users on rollback procedure
  4. Monitor "Rollback History" for audit compliance
  5. Consider adding email notifications on rollback events

Known Limitations

Future Enhancements

Consider implementing: