Cloud sessions accept a hook template upload message and report refusals with a reason.
upload_device_hook_template is handled but refuses whenever hook forwarding is off, which is the default.
What's wrong with this entry?
The cloud-session control channel now handles a new upload_device_hook_template message next to the existing device hook registration. Both refuse when hook forwarding to your machine is turned off, and both now report the refusal reason through the device-hooks registration telemetry.
- Sits behind the same hook-forwarding feature flag and policy checks as device hook registration.
- The message name does not appear in 2.1.241.
upload_device_hook_template
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook