All authors
Claude Skills by tomazb
github.com/tomazb13 skills0 installs13 views
- OperationsGuide the operator through Method 2 switchover: one-time full restore when passive sync is not running. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Method 2](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#method-2-one-time-full-restore-no-prior-passive-sync) ---Votes: 0GitHub stars: 3
- Refactor SimplifySafely simplify a Python module by extracting long methods, consolidating boilerplate, and applying existing patterns. Usage - /refactor-simplify modules/finalization.py or /refactor-simplify --review modules/finalization.pyVotes: 0GitHub stars: 3
- ReleaseBump version across all project files (Python, Bash, Container, Helm, README, CHANGELOG). Usage - /release 1.6.0Votes: 0GitHub stars: 3
- TroubleshootingDiagnose and resolve missing metrics in Grafana dashboards after switchover. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Troubleshooting](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#issue-grafana-shows-no-data-after-15-minutes) ---Votes: 0GitHub stars: 3
- OperationsGuide the operator through Method 1 switchover: disable auto-import, stop Thanos, verify sync, and activate managed clusters via passive restore. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Steps 2-5](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#method-1-continuous-passive-restore-activation-path) ---Votes: 0GitHub stars: 3
- OperationsGuide the operator through safely decommissioning the old primary hub after successful switchover. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Step 14](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#step-14-decommission-old-primary-hub-optional-but-recommended) ---Votes: 0GitHub stars: 3
- OperationsGuide the operator through enabling BackupSchedule on the newly activated hub to resume regular backups. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Steps 11-12](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#step-11-enable-backupschedule-on-new-active-hub) ---Votes: 0GitHub stars: 3
- OperationsGuide the operator through pausing BackupSchedule on the primary hub, with version-specific instructions for ACM 2.11 vs 2.12+. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Step 1](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#step-1-pause-backupschedule-on-primary-hub) **If Argo CD / GitOps manages the BackupSchedule:** Pause Argo CD auto-sync for ACM-touching Applications first (runbook: "Optional: Pause Argo CD Auto-Sync"), or run the switchover tool with `--argocd-manage` so it pauses tho...Votes: 0GitHub stars: 3
- OperationsGuide the operator through ACM switchover pre-flight validation with interactive checks and go/no-go decision points. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Step 0](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#step-0-verify-prerequisites-before-starting-switchover) ---Votes: 0GitHub stars: 3
- OperationsGuide the operator through rolling back to the primary hub if switchover issues occur. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Rollback Procedure](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#rollback-procedure-if-needed) ---Votes: 0GitHub stars: 3
- OperationsGuide the operator through post-activation verification: clusters connected, observability working, metrics flowing. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Steps 6-10](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#post-activation-common-steps-applies-to-both-methods) ---Votes: 0GitHub stars: 3
- TroubleshootingDiagnose and resolve managed clusters stuck in "Pending Import" state after switchover. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Troubleshooting](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#issue-managed-clusters-stuck-in-pending-import) ---Votes: 0GitHub stars: 3
- TroubleshootingDiagnose and resolve ACM Restore resources stuck in "Running" state. > **Reference**: [docs/ACM_SWITCHOVER_RUNBOOK.md — Troubleshooting](../../../docs/ACM_SWITCHOVER_RUNBOOK.md#issue-restore-stuck-in-running-state) ---Votes: 0GitHub stars: 3