pi-herdsman 0.7.2 → 0.7.3
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/dist/index.js +45 -45
- package/docs/guides/recovery.md +21 -0
- package/package.json +1 -1
package/docs/guides/recovery.md
CHANGED
|
@@ -101,6 +101,27 @@ The normal response is to inspect the returned stage/diagnostic and the current
|
|
|
101
101
|
herdr environment. Do not add client-side polling or arbitrary sleeps as an
|
|
102
102
|
operator workaround.
|
|
103
103
|
|
|
104
|
+
Managed Herdr panes must be able to reach their interactive shell prompt
|
|
105
|
+
without requiring human input. Shell startup that waits for a question,
|
|
106
|
+
confirmation, first-run wizard, credential prompt, or similar interaction can
|
|
107
|
+
prevent agent startup.
|
|
108
|
+
|
|
109
|
+
Herdr sets `HERDR_ENV=1` in pane processes, so shell configuration can use that
|
|
110
|
+
marker to disable interactive startup behavior only inside Herdr.
|
|
111
|
+
|
|
112
|
+
For example, with Oh My Zsh, place this before sourcing Oh My Zsh:
|
|
113
|
+
|
|
114
|
+
```zsh
|
|
115
|
+
[[ ${HERDR_ENV:-} == 1 ]] && zstyle ':omz:update' mode disabled
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
Normal terminals keep their configured update behavior; Herdr panes skip
|
|
119
|
+
automatic Oh My Zsh update checks. Run `omz update` manually when desired.
|
|
120
|
+
|
|
121
|
+
If startup still fails, inspect the returned `pane_readiness` stage and bounded
|
|
122
|
+
pane diagnostic rather than adding arbitrary sleeps or automatically answering
|
|
123
|
+
terminal prompts.
|
|
124
|
+
|
|
104
125
|
## Cleanup or rollback failure
|
|
105
126
|
|
|
106
127
|
A `rollback_failure` can contain both:
|
package/package.json
CHANGED