@haakco/hostingctl 1.0.834 → 1.0.850
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 +22 -24
- package/dist/main.js +1419 -858
- package/dist/main.js.map +1 -1
- package/package.json +1 -1
- package/platform/darwin-arm64/hostingctl +0 -0
- package/platform/darwin-x64/hostingctl +0 -0
- package/platform/linux-arm64/hostingctl +0 -0
- package/platform/linux-x64/hostingctl +0 -0
- package/platform/windows-x64/hostingctl.exe +0 -0
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,
|
|
541
|
-
|
|
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
|
|
547
|
+
hostingctl realm attest acme --custd-company <uuid> --owning-user <uuid> --dry-run
|
|
550
548
|
```
|
|
551
549
|
|
|
552
|
-
|
|
553
|
-
|
|
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
|
|
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
|
-
`
|
|
559
|
-
|
|
560
|
-
|
|
561
|
-
|
|
562
|
-
|
|
563
|
-
|
|
564
|
-
|
|
565
|
-
|
|
566
|
-
|
|
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
|
|