@supacloud/cli 0.82.0 → 0.84.0
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 +8 -6
- package/dist/index.js +3273 -174608
- package/dist/shared/tools/app-tools.d.ts +1 -0
- package/dist/shared/tools/application-preview-tools.d.ts +11 -11
- package/dist/shared/tools/application-preview.test.d.ts +1 -0
- package/dist/shared/tools/application-tools.d.ts +1 -1
- package/dist/shared/tools/application-workflow-schemas.d.ts +20 -20
- package/dist/shared/tools/deploy-tools.d.ts +5 -0
- package/dist/shared/tools/frontend-release-control.d.ts +3 -0
- package/dist/shared/transports/http.d.ts +1 -1
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -86,6 +86,7 @@ supacloud-cli app preview-plan --env test --id orders --environment_id test --re
|
|
|
86
86
|
supacloud-cli app preview --env test --id orders --environment_id test --release_id RELEASE_SHA256 --configuration_id CONFIG_UUID --ttl_seconds 3600 --wait --timeout_seconds 300
|
|
87
87
|
supacloud-cli app previews --env test --id orders --environment_id test
|
|
88
88
|
supacloud-cli app preview-status --env test --id orders --environment_id test --preview_id PREVIEW_UUID --wait --timeout_seconds 300
|
|
89
|
+
supacloud-cli app preview-reconcile --env test --id orders --environment_id test --preview_id PREVIEW_UUID
|
|
89
90
|
supacloud-cli app preview-cleanup --env test --id orders --environment_id test --preview_id PREVIEW_UUID
|
|
90
91
|
```
|
|
91
92
|
|
|
@@ -114,9 +115,10 @@ query or identity drift ends it with nonzero status. A wait timeout returns
|
|
|
114
115
|
same-ID continuation in `reconciliation`. It does not mark provisioning failed,
|
|
115
116
|
retry a failed lifecycle GET, delete resources or promote an environment.
|
|
116
117
|
|
|
117
|
-
`preview-plan`
|
|
118
|
-
provisioning
|
|
119
|
-
|
|
118
|
+
`preview-plan`, `previews` and `preview-status` are read-only. They never resume
|
|
119
|
+
persisted provisioning. Use `preview-reconcile` to explicitly resume a selected
|
|
120
|
+
Preview ID; it is classified as a write, including in read-only and production
|
|
121
|
+
profiles. The platform may clean eligible expired
|
|
120
122
|
previews, but never interrupts a serving preview or empties nonempty Storage
|
|
121
123
|
automatically. Explicit cleanup remains available. Failed previews return
|
|
122
124
|
nonzero with the validated receipt and cleanup state. Unknown create outcomes
|
|
@@ -320,14 +322,14 @@ loopback development origins, with the default `:80` likewise omitted. Use
|
|
|
320
322
|
|
|
321
323
|
### Immutable frontend releases
|
|
322
324
|
|
|
323
|
-
The `frontend` command keeps the existing deployment, Git, and
|
|
325
|
+
The `frontend` command keeps the existing deployment, Git, and tar.zst
|
|
324
326
|
actions and also exposes the immutable prebuilt release workflow:
|
|
325
327
|
|
|
326
328
|
```bash
|
|
327
329
|
supacloud-cli frontend list_releases --ref abc123 --id web
|
|
328
330
|
supacloud-cli frontend get_active_release --ref abc123 --id web
|
|
329
331
|
supacloud-cli frontend get_release --ref abc123 --id web --release_id <sha256>
|
|
330
|
-
supacloud-cli frontend upload_release --ref abc123 --id web --
|
|
332
|
+
supacloud-cli frontend upload_release --ref abc123 --id web --archive_path ./dist.tar.zst
|
|
331
333
|
supacloud-cli frontend activate_release --ref abc123 --id web \
|
|
332
334
|
--release_id <sha256> \
|
|
333
335
|
--expected_active_release_id absent \
|
|
@@ -337,7 +339,7 @@ supacloud-cli frontend rollback --ref abc123 --id web --release_id <retained-sha
|
|
|
337
339
|
supacloud-cli frontend rollback --ref abc123 --id web
|
|
338
340
|
```
|
|
339
341
|
|
|
340
|
-
`upload_release` hashes and streams an existing regular
|
|
342
|
+
`upload_release` hashes and streams an existing regular tar.zst file without
|
|
341
343
|
buffering the full archive. The Management API binds the upload to that SHA-256,
|
|
342
344
|
and the CLI reads the immutable release back before reporting success.
|
|
343
345
|
`activate_release` uses both the observed active release and activation IDs as
|