* webhook: share the default target settings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* webhook: managed webhook targets with a drainable queue
Targets kept as JSON (name, endpoint, token, filters, retry and worker
settings) build their own queue; Close waits for queued and in-flight
deliveries before stopping it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: run webhook targets stored in /etc/seaweedfs when notification.webhook.managed is set
The targets in /etc/seaweedfs/notification_webhooks.json start with the
filer and are rebuilt from the store whenever the file changes on any
filer, alongside notification.toml. The previous queue drains before it
stops. Events for the file itself, which holds bearer tokens, are not
sent to notification queues.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* admin: manage filer webhook targets
A Webhooks page under Management lists, adds, edits and deletes the
targets kept in /etc/seaweedfs/notification_webhooks.json. Bearer
tokens are write-only: the API reports whether one is set, and an empty
token on edit keeps the stored one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: keep the webhook queue when the stored targets did not change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: keep a replaced webhook queue open until its senders hand over
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* admin: read chunk-backed webhook targets before editing them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* shell: keep the stored webhook targets out of fs.meta.notify
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* webhook: reject negative managed target settings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* webhook: no signal handler on queues that reloads replace
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: swap the webhook queue without waiting behind blocked senders
The read lock held across SendMessage made a reload wait for any sender
blocked on a saturated target, and the waiting writer stalled every
other filer write with it, which is when an operator disables that
target. Close now refuses new sends and waits for the senders already
inside SendMessage, and a send that hits the closing queue retries on
its replacement.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* webhook: release blocked test handlers before the server shuts down
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: always run the webhook targets managed in the admin UI
Drop the notification.webhook.managed switch: every filer loads and live
reloads the stored targets. Without stored targets no queue is created.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* scaffold: place the admin-managed webhook note above enabled
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* scaffold: separate the admin-managed webhook note
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* scaffold: note that admin-managed webhooks follow the notification queue
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: retry loading webhook targets after a failed read
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: retire the admin-managed webhook queue on shutdown
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Add TraverseBfsWithContext and fix race conditions in error handling
- Add TraverseBfsWithContext function to support context cancellation
- Fix race condition in doTraverseBfsAndSaving using atomic.Bool and sync.Once
- Improve error handling with fail-fast behavior and proper error propagation
- Update command_volume_fsck to use error-returning saveFn callback
- Enhance error messages in readFilerFileIdFile with detailed context
* refactoring
* fix error format
* atomic
* filer_pb: make enqueue return void
* shell: simplify fs.meta.save error handling
* filer_pb: handle enqueue return value
* Revert "atomic"
This reverts commit 712648bc35.
* shell: refine fs.meta.save logic
---------
Co-authored-by: Chris Lu <chris.lu@gmail.com>
* Added a helper function `isHelpRequest()`
* also handles combined short flags like -lh or -hl
* Created handleHelpRequest() helper function
encapsulates both:
Checking for help flags
Printing the help message
* Limit to reasonable length (2-4 chars total) to avoid matching long options like -verbose