Skip to content

fix(dns): use record_id filter for get_dns_settings, not nameserver#194

Merged
chmmou merged 1 commit into
mainfrom
fix/dns-record-id-param
May 30, 2026
Merged

fix(dns): use record_id filter for get_dns_settings, not nameserver#194
chmmou merged 1 commit into
mainfrom
fix/dns-record-id-param

Conversation

@chmmou

@chmmou chmmou commented May 30, 2026

Copy link
Copy Markdown
Owner

dns list exposed a --nameserver flag and sent a nameserver parameter that get_dns_settings does not accept. The KAS contract (and the captured request fixtures) take an optional record_id to narrow the result to a single record.

  • flag --nameserver--record-id, wire param nameserverrecord_id
  • new get_dns_settings single-record fixture wired into a mapping test
  • nameserver is a real KAS key, but for reset_dns_settings, not get_dns_settings

get_dns_settings accepts an optional record_id to narrow the result to
a single record; the read slice had wired a non-existent nameserver
parameter instead. Rename the flag --nameserver -> --record-id and the
wire parameter nameserver -> record_id, matching the KAS contract and
the captured request fixtures. nameserver is a real KAS key but belongs
to reset_dns_settings.
@chmmou chmmou merged commit 28284db into main May 30, 2026
6 checks passed
@chmmou chmmou deleted the fix/dns-record-id-param branch May 30, 2026 15:00
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.

1 participant