@haakco/hostingctl 1.0.817 → 1.0.819

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
@@ -7,16 +7,21 @@ generates its own client from `api/openapi.json`, so its request and response ty
7
7
 
8
8
  Generation does **not** decide which operations have a command — a generated function nobody calls is a
9
9
  feature nobody can use. That accounting lives in `src/commands/operation-map.ts`, which names every published
10
- operation and either the route that reaches it, a shared read, a protocol consumer, a route that exists only to
11
- refuse, or the milestone that owes it a command; `just cli-test` fails when an operation is unaccounted for or a
10
+ operation and either the route that reaches it, a shared read, a protocol consumer, or a route that exists only to
11
+ refuse; `just cli-test` fails when an operation is unaccounted for or a
12
12
  mapped route does not exist.
13
13
 
14
14
  Every published operation is accounted for, and the map holds the current totals rather than this page: each one
15
15
  is reachable from a command, a file route a command redeems with a single-use grant it minted, a protocol consumer
16
16
  the API calls rather than a person, the refusal-only rollback route (the platform refuses every call, and recovery
17
- is a new reviewed release), or a billing operation the panel will own (plan 120). `just cli-test` fails when an
18
- operation is unaccounted for, when a route names a command that does not exist, and when a planned entry is
19
- already reachable.
17
+ is a new reviewed release). Customer and operator operations have commands in both implementations;
18
+ browser authentication ceremonies, provider callbacks and machine consumers retain their protocol owners.
19
+ Coverage is checked against the API document and the commands actually served, not inferred from generation.
20
+
21
+ Secret exports and recovery-code issuance require a new private `--out` file and never print the secret.
22
+ On Windows, use the native client for private-file output: it sets explicit Windows ACLs. The JavaScript
23
+ fallback refuses these operations before requesting a secret because POSIX file modes do not establish
24
+ Windows privacy.
20
25
 
21
26
  ## Install
22
27
 
@@ -234,6 +239,7 @@ own parser (`hostingctl reference`) and compared against it in CI. The groups, i
234
239
  | `backup-destination` | The company's own bucket that also receives its backups |
235
240
  | `backups` | An environment's backup tracks, the newest restore point, and the fresh backup it has asked for: `requests`, `request-show` and the `request` write |
236
241
  | `secret-connection` | An environment's connections to a customer's own secret manager |
242
+ | `provider-connections` | Saved SFTP, FTPS and FTP logins: list, show, add, update, check, check-show, rotate, revoke and remove. Native guided setup or private typed request files; writes require confirmation |
237
243
  | `registry-connections` | A company's container-registry connections: the account, the repository scope, one verified manifest check, credential rotation and revocation. It stores no customer image and starts no workload |
238
244
  | `storage` | Purchased object storage: a capacity's price, the purchase, an increase or a resize at that price, which basis the bucket is billed on, the bucket's connection facts, its keys, objects and bindings, the downloads measured for a month, the ceiling that caps the overage bill, and the optional stored-byte maximum that limits growth without buying capacity |
239
245
  | `company` | The company itself, its members and roles, its activity, its logo and favicon, and the invitation journey |
@@ -264,6 +270,29 @@ Exit status: **0** ok, **1** refused by the API, **2** unusable — bad usage, n
264
270
  API. A refusal prints the API's message, its actionable `detail` when it sent one, and its `X-Request-Id`,
265
271
  which is what joins a failed command to the log line that explains it.
266
272
 
273
+ ## Guided old-host connection setup
274
+
275
+ In the native client, run `hostingctl provider-connections add --company <slug> --confirm` in a terminal.
276
+ Choose the destination environment when there is more than one, then enter the address/login and choose
277
+ a password, a generated SSH key or an existing private-key file. Connection details come from the old
278
+ host's FTP/SSH settings or welcome email. Generated-key setup explains where to authorize its public key.
279
+ Private keys are read from a private local file; they are never command-line arguments.
280
+
281
+ If the login or connection details fail, choose **Edit** to return to the relevant field with your
282
+ other values kept. Use Ctrl+U to replace a hidden password. The saved connection and generated key
283
+ are retained; the screen explains what to correct and where to find it. Session, transport and
284
+ changed-server-identity failures stop with recovery commands rather than silently retrying.
285
+
286
+ The check reports its ID and stages, then offers detected site folders or a typed folder path.
287
+ The old host's File Manager shows the path if it is unclear; Esc keeps the current folder. A changed
288
+ folder is checked again without replacing the saved login or limits.
289
+ If a chosen folder is missing, **Edit** reopens the folder chooser on the same connection. Stopping after
290
+ a failed folder check reports the failure and recovery IDs.
291
+ Read interrupted checks with `provider-connections check-show <check-uuid>` using the same company/API
292
+ settings. No file copy starts
293
+ during setup. Scripts and the JavaScript fallback use a private JSON request via `--file` or `--stdin`;
294
+ `--no-input` on the native command refuses rather than prompting.
295
+
267
296
  ## Quick application speed checks
268
297
 
269
298
  ```sh