feat: make Mittwald database host IP resolution configurable#30
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughA new boolean configuration flag ChangesMittwald hostname resolution opt-in flag
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 PHPStan (2.2.2)PHPStan was skipped because the config uses disallowed Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
mittwald_resolve_host_to_ipflag to control whether the Mittwald database hostname is resolved to its IP and pinned in.envfalseso the DNS hostname is kept — pinning the IP breaks when Mittwald rotates database IPs or enforces TLS against the hostnameBackground
The hostname-to-IP resolution was a workaround for DNS flapping of freshly created Mittwald databases, but it ran unconditionally in two places and now causes problems on Mittwald infrastructure.
Changes
deployer/feature/config/set.php- Addmittwald_resolve_host_to_ipflag (defaultfalse)src/Database/Manager/MittwaldApi.php- GuardresolveHostnameToIp()(setup path)deployer/feature/task/feature_sync.php- GuardresolveDatabaseHostToIp()(sync path)docs/DATABASE.md- Document the flag and updated DNS flapping behaviourSummary by CodeRabbit
New Features
Documentation