How changes are made

Every change Teitunnel makes to your Cloudflare account follows the same four steps.

1. Look. Teitunnel reads the current state: the tunnel, its routes and the DNS records involved.
2. Plan. It works out the smallest set of steps that gets from there to what you asked for, and shows them to you before anything changes. Anything that touches something Teitunnel didn't create is called out and needs your confirmation.
3. Apply. When you confirm, the steps run in order. If Cloudflare changed in the meantime, Teitunnel stops and shows you the new plan instead. If a step fails, every earlier step is undone, and if something can't be undone you're told exactly what was left in place.
4. Verify. Teitunnel checks the hostname through Cloudflare's edge and reports whether it works, and why not if it doesn't.

Activity

Activity records every change: what was asked, each step with how it ended, and what changed before and after, per route and DNS record. From an entry you can:

• Copy All as Commands: the equivalent cloudflared and API calls, to repeat by hand or keep as a record. Secrets appear as $CLOUDFLARE_API_TOKEN, never their values.
• Check a hostname again, if it's still routed.

Filter by kind of change, by domain, or to show only problems.