In this piece of provider code a timeout is set of 15 minutes. The status of the index creation is monitored. The index in Databricks is created and a sync starts. It is normal for this sync to take longer than the timeout and thus the apply fails.
Expected Behavior
Monitor the vector search index and signal a successful create once number of rows synced > 0. Then exit terraform. Do not wait for the full sync. If 1 row is synced, we know the resource was created correctly.
Actual Behavior
After 15 minutes, terraform gives up and removes my search index, which is still syncing.
Steps to Reproduce
Run any vector search creation through terraform where the syncing of data takes longer than the hard-coded timeout of 15 minutes.
Configuration
In this piece of provider code a timeout is set of 15 minutes. The status of the index creation is monitored. The index in Databricks is created and a sync starts. It is normal for this sync to take longer than the timeout and thus the apply fails.
Expected Behavior
Monitor the vector search index and signal a successful create once number of rows synced > 0. Then exit terraform. Do not wait for the full sync. If 1 row is synced, we know the resource was created correctly.
Actual Behavior
After 15 minutes, terraform gives up and removes my search index, which is still syncing.
Steps to Reproduce
Run any vector search creation through terraform where the syncing of data takes longer than the hard-coded timeout of 15 minutes.
Terraform and provider versions
Latest version (on main branch).
Is it a regression?
Not known.
Debug Output
N.A.
Important Factoids
N.A.