4 Commits

Include renames

Author	SHA1	Message	Date
user	0219d7e6e1	test(config): add comprehensive tests for config loading path ... Add tests covering the main configuration loading path which was previously untested (only ClassifyTargets and PSL logic had tests). New test coverage: - New() constructor with default values, env overrides, and error cases - buildConfig() interval parsing with fallback to defaults on invalid input - setupViper() env prefix binding and default value registration - parseCSV() edge cases: whitespace, trailing/leading commas, empty segments - configureDebugLogging() debug mode activation - StatePath() path construction with various DataDir values - ErrNoTargets sentinel error for missing/empty targets - PORT env without DNSWATCHER_ prefix (compatibility) - Target classification into domains vs hostnames via PSL - Invalid targets (public suffixes) rejected with clear error Coverage for internal/config increased from 23% to 92.5%.	2026-03-01 23:56:21 -08:00
clawbotandclawbot	e882e7d237	feat: fail fast when no monitoring targets configured (#75) ... ## Summary When `DNSWATCHER_TARGETS` is empty (the default), dnswatcher previously started successfully and ran indefinitely monitoring nothing. This is a common misconfiguration — forgetting to set the variable or making a typo in its name — and gave no indication anything was wrong. ## Changes - Added `ErrNoTargets` sentinel error in `internal/config/config.go` - Extracted `parseAndValidateTargets()` helper to validate that at least one domain or hostname is configured after target classification - If no targets are configured, dnswatcher now exits with a clear error: `"no monitoring targets configured: set DNSWATCHER_TARGETS environment variable"` - Updated README.md to document that `DNSWATCHER_TARGETS` is required and dnswatcher will refuse to start without it ## How it works The validation runs during config construction (via uber/fx), before the watcher or any other component starts. If `DNSWATCHER_TARGETS` is empty or contains only whitespace/empty entries, `buildConfig()` returns `ErrNoTargets`, which causes fx to fail startup with a clear error message. This is fail-fast behavior: a monitoring daemon with nothing to monitor is a misconfiguration and should not silently run. Closes #69 Co-authored-by: clawbot <clawbot@noreply.git.eeqj.de> Reviewed-on: #75 Co-authored-by: clawbot <clawbot@noreply.example.org> Co-committed-by: clawbot <clawbot@noreply.example.org>	2026-03-02 01:26:55 +01:00
clawbot	73e01c7664	feat: unify DOMAINS/HOSTNAMES into single TARGETS config ... Replace DNSWATCHER_DOMAINS and DNSWATCHER_HOSTNAMES with a single DNSWATCHER_TARGETS env var. Names are automatically classified as apex domains or hostnames using the Public Suffix List (golang.org/x/net/publicsuffix). - ClassifyDNSName() uses EffectiveTLDPlusOne to determine type - Public suffixes themselves (e.g. co.uk) are rejected with an error - Old DOMAINS/HOSTNAMES vars removed entirely (pre-1.0, no compat needed) - README updated with pre-1.0 warning Closes #10	2026-02-19 20:09:39 -08:00
sneak	144a2df665	Initial scaffold with per-nameserver DNS monitoring model ... Full project structure following upaas conventions: uber/fx DI, go-chi routing, slog logging, Viper config. State persisted as JSON file with per-nameserver record tracking for inconsistency detection. Stub implementations for resolver, portcheck, tlscheck, and watcher.	2026-02-19 21:05:39 +01:00