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
**Rationale:** The new name clearly indicates this waits for Route53's internal synchronization, not worldwide DNS propagation (which can take hours depending on TTL values).
84
84
85
-
### JSON Configuration
85
+
### Removed Deprecated Fields
86
86
87
-
If you're using JSON configuration, update your field names:
87
+
Two deprecated fields have been removed in v1.6:
88
88
89
-
**Old (pre-v1.6):**
90
-
```json
91
-
{
92
-
"max_wait_dur": 60,
93
-
"wait_for_propagation": true
89
+
-**`AWSProfile`** → Use `Profile` instead
90
+
-**`Token`** → Use `SessionToken` instead
91
+
92
+
These fields were deprecated several versions ago and have identical functionality to their replacements.
93
+
94
+
```go
95
+
// Old (removed in v1.6)
96
+
provider:= &route53.Provider{
97
+
AWSProfile: "my-profile",
98
+
Token: "my-session-token",
94
99
}
95
-
```
96
100
97
-
**New (v1.6+):**
98
-
```json
99
-
{
100
-
"route53_max_wait": "2m",
101
-
"wait_for_route53_sync": true
101
+
// New (v1.6+)
102
+
provider:= &route53.Provider{
103
+
Profile: "my-profile",
104
+
SessionToken: "my-session-token",
102
105
}
103
106
```
104
107
105
-
Note: The old `max_wait_dur` field accepted a numeric value (seconds), while the new `route53_max_wait` field uses standard Go duration strings like `"2m"`, `"120s"`, etc.
108
+
**JSON Configuration:** If using JSON config, update field names: `aws_profile` → `profile`, `token` → `session_token`
106
109
107
110
## Migration Checklist
108
111
109
112
-[ ] Update to libdns v1.0+ (see libdns documentation for typed records)
110
113
-[ ] Rename `MaxWaitDur` to `Route53MaxWait` in your code
111
114
-[ ] Change from plain integer (e.g., `60`) to proper `time.Duration` (e.g., `60 * time.Second`)
112
115
-[ ] Rename `WaitForPropagation` to `WaitForRoute53Sync` in your code
116
+
-[ ] Replace `AWSProfile` with `Profile` (if using)
117
+
-[ ] Replace `Token` with `SessionToken` (if using)
113
118
-[ ] Update JSON/YAML configuration files with new field names
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,19 @@ When you update records in AWS Route53, changes first propagate internally acros
111
111
112
112
See [Change Propagation to Route 53 DNS Servers](https://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html#API_ChangeResourceRecordSets_RequestSyntax:~:text=Change%20Propagation%20to%20Route%2053%20DNS%20Servers).
113
113
114
+
### Performance optimization for delete operations
115
+
116
+
By default, when `WaitForRoute53Sync` is enabled, the provider waits for synchronization on all operations, including deletes. For bulk delete operations where immediate consistency is not required, you can skip the wait on deletes by setting `SkipRoute53SyncOnDelete` to `true`:
117
+
118
+
```go
119
+
provider:= &route53.Provider{
120
+
WaitForRoute53Sync: true, // Wait for sync on create/update
121
+
SkipRoute53SyncOnDelete: true, // Skip wait on delete for better performance
122
+
}
123
+
```
124
+
125
+
This can significantly speed up bulk delete operations while still maintaining consistency guarantees for create and update operations.
0 commit comments