@haakco/hostingctl 1.0.838 → 1.0.851

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
@@ -537,39 +537,37 @@ describes the change without sending it. `--company` on `transfer` is the client
537
537
 
538
538
  ## Deployment realm lifecycle
539
539
 
540
- Observe one environment's recorded deployment realm, adopt it, retry a failed convergence and record a
541
- workload's audience name. This is the operator path for the environment's CustD realm boundary.
540
+ Observe one environment's recorded deployment realm, retry a failed convergence, and attest the CustD
541
+ authority a company's realms depend on. This is the operator path for the environment's CustD realm
542
+ boundary.
542
543
 
543
544
  ```text
544
545
  hostingctl realm show <environment-uuid> --company acme
545
- hostingctl realm adopt <environment-uuid> --custd-company <uuid> --owning-user <uuid> \
546
- --registration-policy <invite_only|open> --expected-revision <n> [--login-paused] \
547
- [--audiences <path>] --dry-run
548
546
  hostingctl realm retry <environment-uuid> --company acme --confirm
549
- hostingctl realm audience <environment-uuid> <application-uuid> --company acme --audience acme --confirm
547
+ hostingctl realm attest acme --custd-company <uuid> --owning-user <uuid> --dry-run
550
548
  ```
551
549
 
552
- `show` prints what Hosting has recorded for that environment's realm — its state, expected and observed
553
- revisions, whether logins are paused and whether the routes are held — read from the deployment identity the
550
+ No realm is adopted by hand. Once a company is attested, turning sign-in on for an application creates or
551
+ updates its environment's realm. Its audiences, redirect addresses, paused login (exactly while the
552
+ environment is suspended) and invitation-only registration are all derived by Hosting. An environment whose
553
+ applications no longer require sign-in reports `awaiting-application`, because CustD keeps a realm's last
554
+ audience rather than removing it.
555
+
556
+ `show` prints what Hosting has recorded for that environment's realm: its state, expected and observed
557
+ revisions, whether logins are paused and whether the routes are held. It reads the deployment identity the
554
558
  access view already carries, so no new endpoint is added for it. **Recorded convergence is not provider
555
- health, a working sign-in or a released route:** `ready` means the recorded intent converged, and a route
559
+ health, a working sign-in or a released route:** `ready` means the derived state converged, and a route
556
560
  that is not held is not thereby proven live. `--json` carries the API's own deployment-identity object.
557
561
 
558
- `adopt` records the environment's realm allocation intent, and is **platform-addressed**: the staff actor who
559
- may attest a CustD company's authority belongs to no company, so the token needs the platform permission for
560
- it. The authority is existing tenant identity only — the CustD company (`--custd-company`) and its real
561
- owning user (`--owning-user`) — and no provider project, environment or directory identifier is ever an
562
- input. `--registration-policy` is `invite_only` or `open`; `--expected-revision` is the revision the caller
563
- reviewed; `--login-paused` records paused logins; and `--audiences` names a JSON file of audience
564
- registrations in the API's own shape
565
- (`[{"audience":"acme","publicClient":true,"redirectUris":["https://acme.test/callback"]}]`), which the API
566
- validates rather than this CLI inventing registration settings. An omitted file means no recorded audience,
567
- and the API refuses a list that does not match the environment's recorded workload audiences.
568
-
569
- `retry` asks the API to reconcile the realm from its recorded intent: the accepted answer records the retry,
570
- and reconciliation observes the result. `audience` records one application workload's realm audience name
571
- (`--audience`), which the adopted intent then has to match. All three writes need `--confirm`; `--dry-run`
572
- describes the change and sends nothing.
562
+ `attest` is **platform-addressed**: the staff actor who may attest a CustD company's authority belongs to no
563
+ company, so the token needs the platform permission for it. The authority is existing tenant identity only:
564
+ the CustD company (`--custd-company`) and its real owning user (`--owning-user`). No provider project,
565
+ environment or directory identifier is ever an input. Restating the recorded authority is safe; a different
566
+ one is refused.
567
+
568
+ `retry` asks the API to reconcile a failed realm again. The accepted answer records the retry, and
569
+ reconciliation observes the result. Both writes need `--confirm`; `--dry-run` describes the change and sends
570
+ nothing.
573
571
 
574
572
  ## Email service reads
575
573