-
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
databricks_workspace_conf ends up as a bug in terraform apply #564
Milestone
Comments
Can you try surrounding "true" with quotes? |
Hi Serge,
I tried adding quotes to “true”. It still gave the same result.
Thanks & Regards,
Chaitanya KV
[A picture containing drawing Description automatically generated]
From: Serge Smertin ***@***.***>
Sent: Monday, March 15, 2021 2:21 PM
To: databrickslabs/terraform-provider-databricks ***@***.***>
Cc: Koppisetti, Venkata ***@***.***>; Author ***@***.***>
Subject: Re: [databrickslabs/terraform-provider-databricks] databricks_workspace_conf ends up as a bug in terraform apply (#564)
Can you try surrounding "true" with quotes?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/databrickslabs/terraform-provider-databricks/issues/564*issuecomment-799236282__;Iw!!N8Xdb1VRTUMlZeI!23veEiDbg9xiQINCrYFSOqaDuTgjjA2V5ZsvdgfRHvT1nMrjry5ZneHsQjrk6T_h$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASLPX7REPN36JLNWDUGI2OTTDXC7LANCNFSM4ZGDFHQQ__;!!N8Xdb1VRTUMlZeI!23veEiDbg9xiQINCrYFSOqaDuTgjjA2V5ZsvdgfRHvT1nMrjry5ZneHsQq5OqjKS$>.
**********************************************************************
KPMG allows reasonable personal use of the e-mail system. Views and opinions expressed in these communications do not necessarily represent those of KPMG.
*******************************************************************************************************
DISCLAIMER
The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to ***@***.***, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of KPMG are neither given nor endorsed by it.
KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses.
“KPMG”, refers to the platform of Indian delivery entities, which consist of KPMG Global Services Private Limited (“KGSPL”), KPMG Global Services Management Private Limited (“KGSMPL”), KPMG Global Delivery Centre Private Limited (“GDCPL”) and KPMG Resource Centre Private Limited (“KRCPL”). Each platform entity is duly constituted under applicable Indian laws and is either a sub-licensee(s) or controlled party of a member firm of KPMG International Cooperative ("KPMG International"), a Swiss entity that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International Cooperative (“KPMG International”) provides no services to clients. Each member firm of KPMG International Cooperative (“KPMG International”) is a legally distinct and separate entity and each describes itself as such.
*******************************************************************************************************
CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
*******************************************************************************************************
|
Merged
michael-berk
pushed a commit
to michael-berk/terraform-provider-databricks
that referenced
this issue
Feb 15, 2023
* 404 status was handled as resource deletion upon the first Create request, which resulted in `Provider produced inconsistent result after apply` * This commit removes that handling from `common.Resource#Create` and properly propagates error messages back to terraform process * Fixes databricks#564 databricks#576
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
We used databricks_workspace_conf in the terraform code to be able to whitelist some IP addresses on the databricks workspace. The plan stage seems to be fine, but apply stage fails saying this is a bug in terraform.
Terraform Version
Terraform v0.13.2
DataBricks v0.3.1
Affected Resource(s)
Please list the resources as a list, for example:
Environment variable names
None related
Terraform Configuration Files
Debug Output
Expected Behavior
the sent IP list should be added in whitelisting for db workspace
Actual Behavior
Error: Provider produced inconsistent result after apply
When applying changes to module.databricks.databricks_workspace_conf.ipaccess,
provider "registry.terraform.io/databrickslabs/databricks" produced an
unexpected new value: Root resource was present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker
Steps to Reproduce
the above block of code can be placed in the databricks_workspace file to allowlist Ips and try terraform apply. Terraform plan works fine. Apply gives the error
Important Factoids
Are there anything atypical about your accounts that we should know?
None
One similar issue we found
https://github.com/databrickslabs/terraform-provider-databricks/blob/master/docs/resources/ip_access_list.md
The text was updated successfully, but these errors were encountered: