`hermes config get` fills in and masks ${VAR} references, so the Karakeep
MCP entry (env KARAKEEP_API_KEY: ${KARAKEEP_API_KEY}) never matched and
every deploy re-set it and restarted the gateway. It also prints defaults
for unset keys and exits 1 for keys without one. Compare against
~/.hermes/config.yaml itself instead.
`hermes gateway restart` without a terminal refuses while anything is
running unless given --yes (docs, reference/cli-commands); the failed
handler left the gateway restarting under launchd but the play failed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
15 lines
607 B
YAML
15 lines
607 B
YAML
- name: Restart Hermes dashboard
|
|
community.general.launchd:
|
|
name: "{{ hermes_dashboard_label }}"
|
|
state: restarted
|
|
# Nothing to restart in a dry run (on the first deploy the plist isn't there).
|
|
when: not ansible_check_mode
|
|
|
|
# Lets running turns finish first (unlike launchctl kickstart -k). Without a
|
|
# terminal it refuses while turns, cron jobs or subagents are running unless
|
|
# given --yes; the gateway then exits 75 and launchd starts a new one.
|
|
- name: Restart Hermes gateway
|
|
ansible.builtin.command:
|
|
argv: ["{{ hermes_cli }}", gateway, restart, --yes]
|
|
when: not ansible_check_mode
|