Closed viranch closed 1 year ago
Not surprising. Probably other providers have the same issue. I think it's come up with and been fixed in at least once. Suspect the fix will be to see the exists=False
and convert the root NS create to an update in the provider.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Applying a new zone yaml with root NS fails with "record already exists" error, which is likely because the plan wants to create the root NS but after the zone is created, the record also shows up, and trying to create root NS then results in that error.