Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- v0.30.0 still supports the deprecated regional_routing_on field. Configure only one of the two settings.
- Read the effective mode from the admin console or read-only API, then use the matching route_selection value.
- The four values are active-passive-failover, regional-routing, regional-routing-failover, and magicroute.
- Review the plan, read back the setting after applying, and verify routing from existing clients.
Start with the live tailnet’s routing mode
Tailscale’s November 13 Terraform Provider v0.30.0 release added route_selection to tailscale_tailnet_settings. The legacy regional_routing_on field is a Boolean view of the same setting. The API’s regionalRoutingOn returns true only for regional-routing and false for the other three modes.
Before migrating, confirm that Terraform targets the expected tailnet. Check Route selection under General in the admin console, or read routeSelection via the tailnet settings API. A credential scoped to feature_settings:read is sufficient for the API check. Record the mode and target tailnet with the change.
Replace the old field with the value you read back
route_selection accepts four values. active-passive-failover is active-passive failover, regional-routing is regional routing, regional-routing-failover is in-region failover, and magicroute is MagicRoute. Base the migration on the current value from the service.
For example, a team that previously chose MagicRoute in the console may see false in the legacy state. To preserve the mode, set route_selection = "magicroute" and remove regional_routing_on from the Terraform resource configuration. Turning false into active-passive-failover would change the routing policy.
Review the Terraform plan and any other writers
Update the provider through your usual controlled Terraform process and review the plan. The v0.30.0 resource rejects configurations that set both fields. If both appear in state, the provider reads them as two views of one service setting. Inspect the source configuration and resolved module inputs to confirm that only one is explicitly set.
If the plan changes the actual routing mode, replaces the resource, or edits other tailnet settings, investigate before proceeding. Check whether older scripts or a second Terraform configuration still write regionalRoutingOn. Even after the new configuration is correct, another writer can select active-passive failover by writing false.
Read back the setting and check the client path
After applying the reviewed migration through your normal process, read routeSelection again and compare it with the value captured before the change. From an authorized client, test an existing subnet or service and compare the path from the same test point. The setting applies to the entire tailnet. Access and approval rules still determine which connectors are available to a client.
New MagicRoute adoption is limited to eligible Premium or Enterprise tailnets and requires the applicable beta enablement. In-region failover has its own support enablement requirements. During a field migration, preserve the currently available mode. Switching routing policy is a separate network change to validate.
Sources
Frequently Asked Questions
Do I need to edit Terraform state if both attributes appear there?
v0.30.0 reads both attributes, so both can appear in state. The conflict comes from explicitly setting both in configuration. Check the inputs passed by the resource and its modules.
Can I map regional_routing_on: false directly to a new value?
Read routeSelection first. False can represent active-passive failover, in-region failover, or MagicRoute.
Does removing the Terraform resource restore the old routing policy?
The v0.30.0 delete implementation removes the resource from Terraform state and leaves tailnet settings in place. To restore a recorded mode, set it through the normal process, read it back, and verify routing.