Skip to content

Feat/dns force warning - #37

Merged
casablanque-code merged 3 commits into
mainfrom
feat/dns-force-warning
Sep 17, 2026
Merged

casablanque-code merged 3 commits into
mainfrom
feat/dns-force-warning

Conversation

@casablanque-code

Copy link
Copy Markdown
Owner

No description provided.

UpsertCNAME already refused to touch a DNS record it didn't create
unless --force was passed, but once --force *was* passed, the delete
happened silently — no output named what was removed or what it used
to point to.

UpsertCNAME now returns the deleted record (type + content) whenever
it was a foreign one, and 'zt up'/'zt apply' (which both funnel
through createTunnel) print an explicit warning with those details
right where the DNS step already reports success.

This is a printed warning, not a blocking confirmation prompt — same
call made for --public's exposure warning a couple rounds back: an
interactive prompt would break the CI-driven PR-preview workflow
(cfzt-action calls 'zt up' non-interactively). Anyone relying on
--force in automation should treat this warning line as something to
grep their run logs for, not something they'll see live.
Covers all four branches merged this sprint: tunnel-name-validation,
init-hidden-token, env-api-token, tunnel-ownership-tag, plus this
branch's DNS force-delete warning. Bump the version and tag the
release separately, as usual.
@casablanque-code
casablanque-code merged commit dbefc2d into main Sep 17, 2026
4 checks passed
@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 43.75000% with 9 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
internal/cloudflare/dns.go 58.33% 5 Missing ⚠️
cmd/zt/up.go 0.00% 4 Missing ⚠️

📢 Thoughts on this report? Let us know!

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.

2 participants