@supacloud/cli 0.58.4 → 0.59.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 +33 -0
- package/dist/index.js +1394 -61
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -30,6 +30,39 @@ Failed compilation preserves the previous generated artifacts.
|
|
|
30
30
|
Without a config file, an explicit `--root` retains the legacy source-directory
|
|
31
31
|
behavior.
|
|
32
32
|
|
|
33
|
+
### Application delivery
|
|
34
|
+
|
|
35
|
+
```sh
|
|
36
|
+
supacloud-cli app plan --root . --format json
|
|
37
|
+
supacloud-cli app build --root .
|
|
38
|
+
supacloud-cli app upload --ref PROJECT --id orders --manifest_path generated/delivery/delivery.manifest.json
|
|
39
|
+
supacloud-cli app configure --ref PROJECT --id orders --environment_id test --configuration_path configuration.json
|
|
40
|
+
supacloud-cli app deploy --ref PROJECT --id orders --environment_id test --release_id RELEASE_SHA256 --configuration_id CONFIG_UUID --activation_id NEW_UUID --expected_activation_id absent
|
|
41
|
+
supacloud-cli app status --ref PROJECT --id orders --environment_id test
|
|
42
|
+
supacloud-cli app reconcile --ref PROJECT --id orders --environment_id test --release_id RELEASE_SHA256 --activation_id ACTIVATION_UUID
|
|
43
|
+
supacloud-cli app rollback --ref PROJECT --id orders --environment_id test --release_id OLD_RELEASE_SHA256 --configuration_id CONFIG_UUID --activation_id NEW_UUID --expected_activation_id CURRENT_UUID
|
|
44
|
+
supacloud-cli app retire --ref PROJECT --id orders --environment_id test --activation_id ACTIVATION_UUID
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
`plan` and `build` read `delivery` in `supacloud.config.ts`; `--root` is the
|
|
48
|
+
project directory, with sources defaulting to `src`. Plan writes no artifacts.
|
|
49
|
+
Its topology digest is not a release digest or deployment approval. Build needs
|
|
50
|
+
Bun and produces the compiler's immutable manifest beneath configured `outDir`.
|
|
51
|
+
Build, upload and configure only prepare artifacts or configuration, never deploy.
|
|
52
|
+
|
|
53
|
+
Remote actions delegate to `applications` and retain its original receipt,
|
|
54
|
+
identity validation, read-only and production-confirmation checks. Upload returns
|
|
55
|
+
the release ID; configuration writes use the existing JSON contract with an
|
|
56
|
+
explicit revision and expected revision. Deploy and rollback require an explicit
|
|
57
|
+
release, configuration, new activation ID and expected current activation ID.
|
|
58
|
+
Rollback activates the selected old release; it does not downgrade schema or
|
|
59
|
+
restore data. Server compatibility checks still apply.
|
|
60
|
+
|
|
61
|
+
Status returns the server's runtime/readiness report, not an inferred successful
|
|
62
|
+
deployment. An unknown mutation outcome remains unknown; reconcile the same
|
|
63
|
+
activation identity rather than blindly deploying again. These commands require
|
|
64
|
+
Management API credentials except local plan/build and authoring commands.
|
|
65
|
+
|
|
33
66
|
### Framework source upgrades
|
|
34
67
|
|
|
35
68
|
Breaking source-contract changes use the compiler's migration command, which is
|