mholt/caddy-l4

Expose upstream status in admin API

Open

#92 opened on Jan 3, 2023

View on GitHub
 (5 comments) (1 reaction) (0 assignees)Go (114 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1,738 stars)
PR merge metrics
 (Avg merge 14d 19h) (7 merged PRs in 30d)

Description

https://github.com/caddyserver/caddy/pull/4125 introduced an endpoint on the admin API to report upstream statuses for reverse_proxy. It would be nice if caddy-l4 offered something similar.

Contributor guide

Research direction
Review the admin API implementation in caddy l4 to understand how endpoints are registered, then study the upstream status endpoint in caddy's PR #4125 to replicate the pattern.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70