@haakco/hostingctl 1.0.537 → 1.0.539
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 +46 -1
- package/dist/main.js +1045 -63
- package/dist/main.js.map +1 -1
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -204,10 +204,11 @@ metadata and compared against it in CI. The groups, in one line each:
|
|
|
204
204
|
| --- | --- |
|
|
205
205
|
| `whoami`, `environments`, `system`, `diagnostics` | The session's identity and reach, every environment in a company, what the cluster still holds, and the platform's health answer |
|
|
206
206
|
| `watch` | The same environment reads as a screen that refreshes itself. It ships in the Rust build the platform packages carry; the JavaScript bundle has no `watch` |
|
|
207
|
-
| `billing` | The issuer, the price book, the discount codes a client can redeem, a month's run, the invoices and credit notes we issued,
|
|
207
|
+
| `billing` | The issuer, the price book, the discount codes a client can redeem, a month's run, the invoices and credit notes we issued, the client's own documents, and automatic invoice collection |
|
|
208
208
|
| `purchases` | What a company was sold: the record, its size and its term |
|
|
209
209
|
| `backup-destination` | The company's own bucket that also receives its backups |
|
|
210
210
|
| `secret-connection` | An environment's connections to a customer's own secret manager |
|
|
211
|
+
| `storage` | Purchased object storage: a capacity's price, the purchase or an increase at that price, the bucket's connection facts, its keys, objects and bindings |
|
|
211
212
|
| `company` | The company itself, its members and roles, its activity, its logo and favicon, and the invitation journey |
|
|
212
213
|
| `environment` | Create, read, scale, retry; profile coverage, domains and redirects, databases and exports, configuration and secrets, services, site access, shared runtime and application, tools, tuning, retention, portable export, and the release bundle |
|
|
213
214
|
| `application` | Create, rename, remove; build and deploy, build logs, runs and run logs, process schedules; recovery review and confirm; the HTTP cache and path routes; source binding; site access; the WordPress import and URL repair; the administrator credential; the component's publishable anonymous key |
|
|
@@ -787,6 +788,50 @@ environment family reads dedicated web-container output; DNS reports zone-transf
|
|
|
787
788
|
query history; and mail reports a Postfix delivery attempt, which is transport acceptance rather than
|
|
788
789
|
proof of mailbox receipt.
|
|
789
790
|
|
|
791
|
+
## Automatic invoice collection
|
|
792
|
+
|
|
793
|
+
Read whether the platform may collect automatically, where one client's collection stands, and run the
|
|
794
|
+
writes that authorize a method, withdraw it, reconcile a charge nobody can account for, and record money
|
|
795
|
+
received outside Hosting.
|
|
796
|
+
|
|
797
|
+
```text
|
|
798
|
+
hostingctl billing collection status
|
|
799
|
+
hostingctl billing collection show --company acme
|
|
800
|
+
hostingctl billing client collection --company acme
|
|
801
|
+
hostingctl billing collection setup --company acme [--replaces-method <uuid>] --dry-run
|
|
802
|
+
hostingctl billing collection revoke --company acme --method <uuid> [--reason "card lost"] --confirm
|
|
803
|
+
hostingctl billing collection reconcile not-charged --company acme --attempt <uuid> \
|
|
804
|
+
--note "checked the provider dashboard: no transaction" --confirm
|
|
805
|
+
hostingctl billing collection reconcile charged --company acme --attempt <uuid> \
|
|
806
|
+
--note "provider shows a completed transaction" --transaction <provider-ref> \
|
|
807
|
+
--amount 1150.00 --received-at 2026-12-01T10:00:00Z --confirm
|
|
808
|
+
hostingctl billing collection receipt --company acme --invoice <uuid> --transaction <bank-ref> \
|
|
809
|
+
--amount 1150.00 --received-at 2026-12-01T10:00:00Z --note "bank line 42" --confirm
|
|
810
|
+
```
|
|
811
|
+
|
|
812
|
+
`status` reports whether collection is on and ready, and names the configuration items still missing —
|
|
813
|
+
names, never values. `show` reads one company's standing through the platform owner, because a staff
|
|
814
|
+
account is not a member of the company it is looking at; `client collection` reads the same standing
|
|
815
|
+
through the customer route the caller's own token can reach. Both print the recorded method and each
|
|
816
|
+
invoice's derived position, its next collection and any recorded reason a send is blocked.
|
|
817
|
+
|
|
818
|
+
`setup` records the consent and creates a method that is **pending**: nothing is authorized, and no invoice
|
|
819
|
+
can be charged, until the provider confirms the card in a browser. The provider's signed form is
|
|
820
|
+
deliberately not printed — its fields carry the merchant's own credentials — so a terminal starts the
|
|
821
|
+
authorization and the browser completes it. `revoke` stops future charges immediately; a charge the
|
|
822
|
+
provider has already accepted may still settle, and the standing shows it as it happens.
|
|
823
|
+
|
|
824
|
+
`reconcile` records what happened to a charge nobody can account for: `not-charged` makes the invoice
|
|
825
|
+
collectable again, and `charged` records the settlement from the provider's own transaction id, which is
|
|
826
|
+
what makes recording the same one twice the same fact rather than a second payment. `receipt` records money
|
|
827
|
+
received outside Hosting against one invoice, attributed to the operator who verified it. Both require
|
|
828
|
+
`--note`: what was checked and where. That is the point — a settlement nobody had to explain cannot be
|
|
829
|
+
recorded from here, which is why `receipt` refuses a missing note even though the API would accept a null
|
|
830
|
+
one.
|
|
831
|
+
|
|
832
|
+
Every write needs `--confirm`; `--dry-run` describes the change and sends nothing. No command prints a
|
|
833
|
+
token, a provider method handle or a credential.
|
|
834
|
+
|
|
790
835
|
## What it never does
|
|
791
836
|
|
|
792
837
|
No cluster or database access, ever. Those credentials belong to the platform, and a client's laptop is not
|