Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Trigger Manual Container Update Scans #543

Closed
Kalougear opened this issue Jan 5, 2025 · 1 comment
Closed

Unable to Trigger Manual Container Update Scans #543

Kalougear opened this issue Jan 5, 2025 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@Kalougear
Copy link

Kalougear commented Jan 5, 2025

Description

Currently unable to trigger immediate container update scans via either MQTT or HTTP endpoints. The service receives commands but doesn't initiate scans, only showing "Listening to docker events" in logs.

Current Behavior

  • Service receives MQTT messages/HTTP requests
  • Logs only show: "Listening to docker events"
  • No scan is initiated
  • No response or acknowledgment is returned

Expected Behavior

  • Ability to trigger immediate container update scans via MQTT or HTTP endpoint
  • Confirmation of scan initiation
  • Scan results returned via configured channels

Configuration Used

environment:
  # MQTT Configuration
  - WUD_TRIGGER_MQTT_LOCAL_URL=mqtt://host:1883
  - WUD_TRIGGER_MQTT_LOCAL_USER=user
  - WUD_TRIGGER_MQTT_LOCAL_PASSWORD=pass
  - WUD_TRIGGER_MQTT_LOCAL_TOPIC=wud_test/updates

  # HTTP Configuration
  - WUD_TRIGGER_HTTP_SCAN_URL=http://localhost:3100/trigger/scan
  - WUD_TRIGGER_HTTP_SCAN_METHOD=POST

Steps to Reproduce

Send MQTT message to wud_test/updates/trigger:

{
  "name": "container_name",
  "watcher": "local",
  "type": "trigger"
}

Or send HTTP POST to http://localhost:3100/trigger/scan
Check logs - only shows "Listening to docker events"

Environment

WUD Version: latest
OS: Debian
Docker.

Additional Context

Regular scheduled scans via CRON work correctly
Container events are being monitored successfully
Need ability to trigger immediate scans for automation purposes

PLUS

Can i trigger an update with this methods?

@fmartinou
Copy link
Collaborator

Hi,

I think there is a misunderstanding regarding triggers.

Triggers are not intended to execute something on wud.
They are intended to trigger external actions (sending a notification via telegram...)

The http trigger allows to run external webhooks.
These webhooks have to be coded and deployed somewhere.
What happens next exclusively depends on on what will have been implemented on the webhook backend.

Same for mqtt ;wud is not able to receive commands through mqtt for now.

If you want to programmatically trigger things on wud, you can use the wud api:

@fmartinou fmartinou self-assigned this Jan 10, 2025
@fmartinou fmartinou added the question Further information is requested label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants