@supacloud/admin 0.24.2 → 0.26.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 +13 -0
- package/dist/index.js +11283 -7841
- package/package.json +5 -2
package/README.md
CHANGED
|
@@ -70,6 +70,7 @@ production requires the exact project ref confirmation:
|
|
|
70
70
|
|
|
71
71
|
```bash
|
|
72
72
|
supacloud-admin frontend list_releases --ref abc123 --id web
|
|
73
|
+
supacloud-admin frontend get_active_release --ref abc123 --id web
|
|
73
74
|
supacloud-admin frontend get_release --ref abc123 --id web --release_id <sha256>
|
|
74
75
|
supacloud-admin frontend upload_release --ref abc123 --id web \
|
|
75
76
|
--zip_path /secure/site.zip --confirm-production abc123
|
|
@@ -77,6 +78,10 @@ supacloud-admin frontend activate_release --ref abc123 --id web \
|
|
|
77
78
|
--release_id <sha256> --expected_active_release_id absent \
|
|
78
79
|
--expected_activation_id absent --mutation_id <uuid-v4> \
|
|
79
80
|
--confirm-production abc123
|
|
81
|
+
supacloud-admin frontend rollback --ref abc123 --id web \
|
|
82
|
+
--release_id <retained-sha256> --confirm-production abc123
|
|
83
|
+
supacloud-admin frontend rollback --ref abc123 --id web \
|
|
84
|
+
--confirm-production abc123
|
|
80
85
|
```
|
|
81
86
|
|
|
82
87
|
The CLI reads the archive through a no-follow file descriptor, verifies its
|
|
@@ -88,6 +93,14 @@ activation mutations require the Linux held-directory-FD implementation; on
|
|
|
88
93
|
other platforms, Management API returns HTTP 503 before it reads the upload
|
|
89
94
|
body, creates release directories, or writes a mutation journal.
|
|
90
95
|
|
|
96
|
+
The active snapshot automatically supports older HTTP 404 endpoints through
|
|
97
|
+
bounded history and exact artifact readback, never authorization or integrity
|
|
98
|
+
failures. `rollback` handles current CAS and mutation IDs automatically, defaulting
|
|
99
|
+
to a journal-verified previous retained target. An explicit target is still
|
|
100
|
+
supported for deliberate rollback. It never retries a concurrent conflict,
|
|
101
|
+
restores a database or infers a target from sorted history.
|
|
102
|
+
Unknown results include the mutation ID for read-only reconciliation.
|
|
103
|
+
|
|
91
104
|
SSH host keys are fail-closed: setting `SUPACLOUD_HOST` and credentials is not
|
|
92
105
|
enough to enable SSH actions. Obtain the fingerprint through a trusted channel,
|
|
93
106
|
compare it out of band, then set it explicitly. For example, the discovery
|