also looking at this
feat(operations): fleet inventory, attach preflight, and the exports that were missing
#192
11 files
+1313
-5
| @@ -0,0 +1,25 @@ | ||
| 1 | /** | |
| 2 | * Fleet operations: plan-then-apply changes to live topology. | |
| 3 | * | |
| 4 | * Consolidating servers - moving an app to another box, attaching one as a | |
| 5 | * site, renaming a box, tearing a drained one down - is a routine cleanup that | |
| 6 | * is otherwise an afternoon of SSH. Every operation here is expressed as an | |
| 7 | * {@link OperationPlan}: it says what it would change before touching anything, | |
| 8 | * each step asks reality whether it is already satisfied so a run that died | |
| 9 | * halfway resumes by being run again, irreversible steps are gated on typed | |
| 10 | * confirmation, and nothing reads stdin so the whole sequence drives from CI. | |
| 11 | * | |
| 12 | * These modules existed for several releases without being exported, so they | |
| 13 | * type-checked on import and threw at runtime. This barrel is what makes them | |
| 14 | * reachable. | |
| 15 | * | |
| 16 | * @see https://github.com/stacksjs/ts-cloud/issues/167 | |
| 17 | * @see https://github.com/stacksjs/ts-cloud/issues/191 | |
| 18 | */ | |
| 19 | ||
| 20 | export * from './drained-sites' | |
| 21 | export * from './inventory' | |
| 22 | export * from './plan' | |
| 23 | export * from './server-rename' | |
| 24 | export * from './site-attach' | |
| 25 | export * from './site-move' | |