@haakco/hostingctl 1.0.870 → 1.0.875

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -549,15 +549,24 @@ boundary.
549
549
 
550
550
  ```text
551
551
  hostingctl realm show <environment-uuid> --company acme
552
+ hostingctl realm prepare <environment-uuid> <workload-uuid> --company acme --confirm
553
+ hostingctl realm activate <environment-uuid> <workload-uuid> <release-uuid> --company acme --confirm
554
+ hostingctl realm retire <environment-uuid> <workload-uuid> <release-uuid> --company acme --confirm
552
555
  hostingctl realm retry <environment-uuid> --company acme --confirm
553
556
  hostingctl realm attest acme --custd-company <uuid> --owning-user <uuid> --dry-run
554
557
  ```
555
558
 
556
- No realm is adopted by hand. Once a company is attested, turning sign-in on for an application creates or
557
- updates its environment's realm. Its audiences, redirect addresses, paused login (exactly while the
558
- environment is suspended) and invitation-only registration are all derived by Hosting. An environment whose
559
- applications no longer require sign-in reports `awaiting-application`, because CustD keeps a realm's last
560
- audience rather than removing it.
559
+ Once a company is attested, turning sign-in on for a new application creates or updates its environment's
560
+ realm. For an existing Keycloak application, `prepare` queues a CustD realm and audience while Keycloak
561
+ continues serving. Repeat preparation after the existing member accepts the invitation to reconcile the
562
+ target grant. Hosting derives each realm's audiences, redirect addresses, and invitation-only registration.
563
+ Login pauses while the environment is suspended. A realm whose applications no longer require sign-in
564
+ reports `awaiting-application` because CustD retains its last audience.
565
+
566
+ `activate` puts the specified candidate into rollout with the prepared CustD issuer. The candidate must
567
+ declare the matching issuer, JWKS endpoint, audience, group, and workload identifier, and preserve
568
+ the running application's mounts. After verifying the live sign-in and application data, `retire`
569
+ removes the former Keycloak client and group for that application.
561
570
 
562
571
  `show` prints what Hosting has recorded for that environment's realm: its state, expected and observed
563
572
  revisions, whether logins are paused and whether the routes are held. It reads the deployment identity the