provider/aws: Allow Route53 records creation to be optionally non-blocking

[radeksimko]

If a user is creating DNS records via Route53, it's currently waiting until the record is propagated (which may take quite some time). It's effectively waiting for Status=INSYNC

Similarly to RDS instances, user may not want to wait for it, if the resource is not intended to be used elsewhere in the graph.

To solve both cases (currently RDS & Route53), would be any value/interest in adding something like -non-blocking option to terraform apply and terraform destroy which would automatically skip WaitForState() if the graph allows it?
I just don't know from the top of my head what else could be affected unintentionally by this.

[scalp42]

+1 It's really painful

[phinze]

I'm going to close this, because I believe taking the opposite position (that each resource must block until it can guarantee that the resource is ready to perform service) is important for the Terraform project to take generally in order to maintain the integrity of the dependency graph.

Feel free to follow up if you'd like to discuss further. 👍

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.