You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a523ee5
Browse filesBrowse the repository at this point in the historyBrowse files
Add static DNS (v2 site API) to the legacy adapter (#18)
Controller-local DNS records were reachable from nothing but curl. Homelab needs
them to declare internal names as IaC and to stop LAN access to the Pangolin-fronted
zones depending on NAT hairpin.
Static DNS lives on the v2 site API, which shares the host and the auth with the legacy
surface but none of its conventions: bare JSON arrays instead of the {meta,data}
envelope, and updates that are full replacements — a PUT carrying only the changed field
is answered 400 Validation failed, where the legacy rest/user path accepts exactly that.
Treating them alike compiles and passes every unit test, then fails against a real
controller, so the difference is encoded in the types: UnifiStaticDnsRecord is
non-nullable throughout and a test pins that every field serializes even at its default.
Options gains Site (parsed from the base URL, not assumed) and SiteV2Url; the session
gains SendAbsoluteAsync, since a v2 path cannot be reached relative to the legacy base.
Auth, TLS and the 401 policy are unchanged and shared.
All four verbs were probed against the live controller before any of it was written, and
wildcard keys confirmed to match arbitrary labels. Bumps to 0.3.0.
0 commit comments