Value Statement

Unify all restore operations (sync, non-sync, partial restore, and full restore) under a consistent, predictable execution model with well-defined ordering rules:

1. *Passive resources are always restored first*
2. *Active resources are always restored second* (after all passive resources complete and before managed clusters begin restoration, when applicable)

All restore scenarios now follow the same predictable pattern regardless of sync mode, phase, or backup name combinations. The consistent ordering model improves code maintainability and provides reliable, deterministic restore behavior across all scenarios.
 
 

1. 1. Summary

This change refactors the restore controller architecture to make active/passive resource restoration more explicit and maintainable.

1. 1. 1. How Backup Files Are Restored:

Each backup is now restored using a dual-restore approach that separates passive and active resources:

1. *Credentials Backup* (`acm-credentials-schedule`) generates two restore operations:
-`restore-acm-credentials-schedule-20260225160046` - restores passive resources
-`restore-acm-credentials-schedule-20260225160046-active` - restores active resources (cluster-activation labeled)

2. *Generic Resources Backup* (`acm-generic-resources-schedule`) generates two restore operations:
-`restore-acm-generic-resources-schedule-20260225160046` - restores passive resources
-`restore-acm-generic-resources-schedule-20260225160046-active` - restores active resources (cluster-activation labeled)

3. *Resource Filtering*: The `-active` suffixed restores target resources labeled with `cluster-activation` from their corresponding backup, while regular restores (no suffix) handle all other resources (NotIn cluster-activation label)

4. *Execution Order*: The `-active` restores execute after all regular restores complete and before managed cluster restoration begins, ensuring passive resources are fully restored before activating cluster-specific resources

Definition of Done for Engineering Story Owner (Checklist)

• ACM Restore works and all passive resources are restored before active resources, in a sync or regular restore.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.