Skip to content

Trigger immediate backend health check after add or enable - #32

Merged
ktrubilo9 merged 2 commits into
mainfrom
feat/iss-21
Aug 26, 2026
Merged

ktrubilo9 merged 2 commits into
mainfrom
feat/iss-21

Conversation

@ktrubilo9

@ktrubilo9 ktrubilo9 commented Aug 26, 2026

Copy link
Copy Markdown
Owner

What

Trigger an immediate health check after a backend is added or enabled.

Previously, a new or enabled backend stayed inactive until the next periodic health-check cycle.

Changes

  • trigger an async health check after adding an enabled backend
  • trigger an async health check after enabling a backend
  • keep failed backends inactive
  • keep the existing periodic health checks
  • add tests for add and enable flows

Tests

  • add enabled backend + healthy → active
  • add enabled backend + unhealthy → inactive
  • enable disabled backend + healthy → active
  • enable disabled backend + unhealthy → inactive

go test ./...

Closes #21

@ktrubilo9
ktrubilo9 merged commit f614c92 into main Aug 26, 2026
1 check passed
@ktrubilo9 ktrubilo9 self-assigned this Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Trigger health checks after backend add and enable operations

1 participant