[deployer] Organizations: manage an organization (its admin instance and member instances) as one unit

mik-tf commented

2026-06-15 22:53:17 +00:00

Owner

Creating many member instances at once (home#288) produces the member instances, but the operator then needs to manage them as one living organization rather than as many separate machines. An organization is a named instantiation of the Hero platform for one company, team, or class: one admin instance plus its member instances, created from a saved setup and a release channel. The operator should be able to open an organization and see it as a whole (how many member instances, how many healthy, which build they are on), update the whole organization to the latest build in one action, and grow or shrink it (add or remove members) without rebuilding it. This is the layer that lets a deployment be stood up once and then evolve in place: at a chosen moment the operator refreshes the whole organization to the newest stack. It builds on organization creation and on the existing update all machinery, made organization aware and channel aware. Each member instance created by organization creation should already carry its organization, setup, and channel so this layer can manage it without a rebuild. Part of the composable provisioning product tracked at home#285.

Signed-by: mik-tf mik-tf@noreply.invalid

Creating many member instances at once (home#288) produces the member instances, but the operator then needs to manage them as one living organization rather than as many separate machines. An organization is a named instantiation of the Hero platform for one company, team, or class: one admin instance plus its member instances, created from a saved setup and a release channel. The operator should be able to open an organization and see it as a whole (how many member instances, how many healthy, which build they are on), update the whole organization to the latest build in one action, and grow or shrink it (add or remove members) without rebuilding it. This is the layer that lets a deployment be stood up once and then evolve in place: at a chosen moment the operator refreshes the whole organization to the newest stack. It builds on organization creation and on the existing update all machinery, made organization aware and channel aware. Each member instance created by organization creation should already carry its organization, setup, and channel so this layer can manage it without a rebuild. Part of the composable provisioning product tracked at home#285. Signed-by: mik-tf <mik-tf@noreply.invalid>

mik-tf added the

platform

label

2026-06-15 22:53:17 +00:00

~~mik-tf referenced this issue 2026-06-15 22:53:17 +00:00~~

[deployer] Composable provisioning product: app catalog, saved setups, and organization creation #285

~~mik-tf referenced this issue 2026-06-15 22:53:17 +00:00~~

[deployer] Create many member instances at once from a saved setup and a list of names #288

mik-tf changed title from ~~[deployer] Organizations: manage a group of Hero platforms as one unit (status, update to latest, grow and shrink)~~ to [deployer] Organizations: manage an organization (its admin instance and member instances) as one unit

2026-06-16 00:22:32 +00:00

~~mik-tf referenced this issue 2026-06-16 05:58:55 +00:00~~

[deployer] Launcher: compose setups, members, and organizations into deployments #291

Rows
Columns

[deployer] Organizations: manage an organization (its admin instance and member instances) as one unit #289