@walkeros/cli 4.2.0 → 4.2.1-next-1781538735002
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/CHANGELOG.md +39 -0
- package/dist/cli.js +822 -381
- package/dist/index.d.ts +879 -114
- package/dist/index.js +844 -399
- package/dist/index.js.map +1 -1
- package/openapi/spec.json +2543 -1442
- package/package.json +8 -8
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,44 @@
|
|
|
1
1
|
# @walkeros/cli
|
|
2
2
|
|
|
3
|
+
## 4.2.1-next-1781538735002
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- b03bfce: `walkeros deploy` now waits long enough to cover a full server deploy
|
|
8
|
+
by default, so a slow but healthy deploy is no longer aborted early and
|
|
9
|
+
reported as a failure. Each run sends a fresh idempotency key, so retrying
|
|
10
|
+
after a failure starts a new deploy instead of replaying the previous result.
|
|
11
|
+
Failures print a stable, machine-readable error code (with a `Retry-After`
|
|
12
|
+
hint on rate limits), and `deploy create` no longer prints an empty token
|
|
13
|
+
placeholder.
|
|
14
|
+
- ec84331: The managed flow runner now retries its bundle, config, and secret
|
|
15
|
+
fetches on transient failures (timeouts, network errors, 5xx) with bounded,
|
|
16
|
+
jittered backoff capped well inside the container health window, and the
|
|
17
|
+
secret fetch is now bounded by a timeout. A brief outage while a flow
|
|
18
|
+
container starts no longer hard-fails the run.
|
|
19
|
+
- 4809699: The managed flow runner now reports its recent errors and recent log
|
|
20
|
+
output in its heartbeat, so deployed flows can surface runtime errors and logs
|
|
21
|
+
in the app without any external log tooling. Secrets are redacted before
|
|
22
|
+
leaving the runner.
|
|
23
|
+
- 5cbcd23: `walkeros run` reads two new environment variables.
|
|
24
|
+
`WALKEROS_OBSERVE_LEVEL` sets the runtime's baseline telemetry level (`off`,
|
|
25
|
+
`standard`, or `trace`). `WALKEROS_CONFIG_FROZEN` (`1` or `true`) serves the
|
|
26
|
+
bundle as an immutable snapshot: secrets are still injected at boot, but
|
|
27
|
+
config hot-swap and heartbeat are disabled.
|
|
28
|
+
- 5cbcd23: All four simulate functions (`simulateSource`, `simulateTransformer`,
|
|
29
|
+
`simulateCollector`, `simulateDestination`) accept a new `data` option to run
|
|
30
|
+
an existing bundle with updated configuration values, without rebundling. The
|
|
31
|
+
new `buildDataPayload`, `classifyStepProperties`, and `containsCodeMarkers`
|
|
32
|
+
exports build and inspect that payload. Destination simulation results now
|
|
33
|
+
include `mappingKey`, the entity-action key of the matched mapping rule.
|
|
34
|
+
- Updated dependencies [bd9188d]
|
|
35
|
+
- Updated dependencies [5cbcd23]
|
|
36
|
+
- @walkeros/collector@4.2.1-next-1781538735002
|
|
37
|
+
- @walkeros/core@4.2.1-next-1781538735002
|
|
38
|
+
- @walkeros/server-core@4.2.1-next-1781538735002
|
|
39
|
+
- @walkeros/server-destination-api@4.2.1-next-1781538735002
|
|
40
|
+
- @walkeros/transformer-validate@4.2.1-next-1781538735002
|
|
41
|
+
|
|
3
42
|
## 4.2.0
|
|
4
43
|
|
|
5
44
|
### Minor Changes
|