feat(plugin-catalog): add ntfy-approval
Answer Hermes' approval prompts from an ntfy push notification with Approve once, Approve for session and Deny buttons; silence still denies. An approval transport (register_approval_transport): the phone posts a one-time answer code to a reply topic, so nothing listens on the Hermes machine.
This commit is contained in:
27
plugin-catalog/ntfy-approval.yaml
Normal file
27
plugin-catalog/ntfy-approval.yaml
Normal file
@@ -0,0 +1,27 @@
|
||||
name: ntfy-approval
|
||||
repo: https://github.com/AhmetArif0/hermes-ntfy-approval
|
||||
sha: e6d557073d7034002503c27113b80df1c64b3485
|
||||
subdir: ntfy-approval
|
||||
description: >-
|
||||
Answer Hermes' approval prompts from your phone: once selected with
|
||||
security.approval.transport: ntfy, each dangerous-command prompt arrives as an ntfy push
|
||||
notification with Approve once, Approve for session and Deny buttons, and no answer still
|
||||
means deny. Disclosure — registers the ntfy approval transport (inactive until selected) and
|
||||
the `hermes ntfy-approval setup|test` command; only while an approval (or `test`) is pending
|
||||
it connects to the configured ntfy server (https://ntfy.sh by default) to publish one
|
||||
notification (Hermes' reason, the command as Hermes redacted it unless send_command is false,
|
||||
and one-time answer codes), read the reply topic and then delete the notification; reads
|
||||
NTFY_APPROVAL_TOPIC and NTFY_APPROVAL_TOKEN from the profile's .env and never puts the token
|
||||
in a notification; writes no files, starts no processes or threads, and follows no redirects.
|
||||
maintainer: AhmetArif0
|
||||
tier: community
|
||||
category: automation
|
||||
requires_hermes: ">=0.21.5"
|
||||
docs_url: https://github.com/AhmetArif0/hermes-ntfy-approval
|
||||
version: "1.0.0"
|
||||
platforms: []
|
||||
capabilities:
|
||||
provides_tools: []
|
||||
provides_hooks: []
|
||||
provides_middleware: []
|
||||
requires_env: []
|
||||
Reference in New Issue
Block a user