Add creation timeout parameter for resource cluster #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per Confluent documentation, provisioning of dedicated clusters can take up to 24 hours. However, provisioning of clusters failed at due to context deadline being exceeded after 20 minutes (as per tf documentation, it's a default). This PR by @borisnaydis tried to address the issue, but changes did not remediate it. This PR adds a configurable timeout parameter for creation of clusters, which defaults to 24 hours, but can be changed in the resource configuration (snippet below). Code is tested locally and with this change it is possible to provision larger clusters to confluent without facing a timeout at around 20 minutes.