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
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
Applying Terraform configuration to Google Cloud Platform always fails the first time but succeeds the second time if DNS records are being changed (rather than added or deleted).
The underlying cause is a race condition since changing a record actually just deletes the old one and creates a new one. The delete stage takes longer than the create stage, so when Terraform attempts to create the new record, the old one still exists and an error is returned by GCP. This is because Terraform seems to run steps in parallel.
This may have been fixed in a later Google provider update, but to know for sure, we need to upgrade our Terraform and provider versions to the latest available.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Applying Terraform configuration to Google Cloud Platform always fails the first time but succeeds the second time if DNS records are being changed (rather than added or deleted).
The underlying cause is a race condition since changing a record actually just deletes the old one and creates a new one. The delete stage takes longer than the create stage, so when Terraform attempts to create the new record, the old one still exists and an error is returned by GCP. This is because Terraform seems to run steps in parallel.
This may have been fixed in a later Google provider update, but to know for sure, we need to upgrade our Terraform and provider versions to the latest available.
The text was updated successfully, but these errors were encountered: