-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE] Terraform Meta Block "timeouts" Reporting as Unsupported #1142
Comments
there is no support for such block in SQL Endpoints - refer to documentation for supported parameters. The Terraform documentation says that "some resources" support it, not "all resources" support it. Please file feature request, or better, PR if you need such functionality. |
@alexott sql endpoints did actually suppose to have working timeouts, this is something to investigate for next week |
@alexott As per the document you shared the timeout is supported. Can you please double check |
@kuntalkumarbasu we'll investigate this as soon as we can. stay tuned. |
Previously, `timeout` meta-block was documented, but resulting in error. It was due to `Timeouts: &schema.ResourceTimeout` not added on resource. Fixes #1142
Previously, `timeout` meta-block was documented, but resulting in error. It was due to `Timeouts: &schema.ResourceTimeout` not added on resource. Fixes #1142
Previously, `timeout` meta-block was documented, but resulting in error. It was due to `Timeouts: &schema.ResourceTimeout` not added on resource. Fixes databricks#1142
Hi there,
Configuration
Expected Behavior
Should have used the extra Terraform resource meta argument and extended the creation timeout built into terraform.
Actual Behavior
Error message from terraform:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
Terraform and provider versions
$ terraform -v
Terraform v0.13.7
Debug Output
Please add turn on logging, e.g.
TF_LOG=DEBUG terraform apply
and run command again, paste it to gist & provide the link to gist. If you're still willing to paste in log output, make sure you provide only relevant log lines with requests.It would make it more readable, if you pipe the log through
| grep databricks | sed -E 's/^.* plugin[^:]+: (.*)$/\1/'
, e.g.:If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the
crash.log
.Important Factoids
Are there anything atypical about your accounts that we should know?
N/A
The text was updated successfully, but these errors were encountered: