@runveric/cli 0.1.2 → 0.2.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 +29 -3
- package/dist/runveric.mjs +1188 -144
- package/dist/runveric.mjs.map +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
production runner image — without pushing anything or signing in.**
|
|
5
5
|
|
|
6
6
|
```sh
|
|
7
|
-
npx @runveric/cli@0.
|
|
7
|
+
npx @runveric/cli@0.2.0 init --id yourteam/restart-web-tier
|
|
8
8
|
```
|
|
9
9
|
|
|
10
10
|
---
|
|
@@ -39,7 +39,7 @@ script outside the platform. Nothing in the product offered that. This does.
|
|
|
39
39
|
## Install
|
|
40
40
|
|
|
41
41
|
```sh
|
|
42
|
-
npx @runveric/cli@0.
|
|
42
|
+
npx @runveric/cli@0.2.0 <command> # no install
|
|
43
43
|
npm install -g @runveric/cli # or install the `runveric` bin
|
|
44
44
|
```
|
|
45
45
|
|
|
@@ -62,7 +62,7 @@ Pin the version your Runveric deployment shows you on its Author page rather tha
|
|
|
62
62
|
Scaffold a PowerShell action, look at what you got, validate it, and run it locally:
|
|
63
63
|
|
|
64
64
|
```sh
|
|
65
|
-
$ npx @runveric/cli@0.
|
|
65
|
+
$ npx @runveric/cli@0.2.0 init restart-web-tier \
|
|
66
66
|
--id acme/restart-web-tier \
|
|
67
67
|
--interpreter powershell \
|
|
68
68
|
--yes
|
|
@@ -164,6 +164,32 @@ Publishing does not adopt. Nobody can run it until somebody chooses to.
|
|
|
164
164
|
|
|
165
165
|
---
|
|
166
166
|
|
|
167
|
+
## Publishing first-party catalog artifacts (`runveric catalog`)
|
|
168
|
+
|
|
169
|
+
Not part of authoring, and not something an author needs. The product's own catalog is pinned
|
|
170
|
+
from immutable artifacts published by its action and catalog repositories, and their workflows
|
|
171
|
+
publish with these two commands:
|
|
172
|
+
|
|
173
|
+
```sh
|
|
174
|
+
# one action's manifest, verbatim — stdout: <key>=<repository>@<digest>
|
|
175
|
+
npx @runveric/cli@0.2.0 catalog publish-action --manifest catalog.yaml \
|
|
176
|
+
--to ghcr.io/<org>/action-azure-vm-stop
|
|
177
|
+
|
|
178
|
+
# a release naming each action artifact by digest — stdout: <repository>@<digest>
|
|
179
|
+
npx @runveric/cli@0.2.0 catalog publish-release --from release.yaml --to ghcr.io/<org>/catalog
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
An action's package must be named after its key (`azure.vm.stop` → `action-azure-vm-stop`); the
|
|
183
|
+
CLI refuses any other name before pushing, and the server refuses it again when a release is
|
|
184
|
+
planned or pinned. Neither command validates a manifest — the server does, every time. Publishing
|
|
185
|
+
makes an artifact available; only a pin makes it live.
|
|
186
|
+
|
|
187
|
+
Credentials: `GHCR_TOKEN` (a token with `write:packages`), or in a workflow `GITHUB_TOKEN` with
|
|
188
|
+
`packages: write`. Provenance comes from `--repository`/`--commit`, else GitHub Actions'
|
|
189
|
+
environment, else git.
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
167
193
|
## Supply chain
|
|
168
194
|
|
|
169
195
|
Every release is published from CI on a tag, with [npm
|