Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When SQL Analytics is not enabled on the workspace, the error message from the backend is not propagated #576

Closed
nfx opened this issue Mar 25, 2021 · 1 comment
Closed

When SQL Analytics is not enabled on the workspace, the error message from the backend is not propagated #576

nfx opened this issue Mar 25, 2021 · 1 comment
Assignees
@nfx
Milestone
v0.3.2

Comments

@nfx
Copy link
Contributor

nfx commented Mar 25, 2021

Provider produced inconsistent result after apply appears instead of FEATURE_DISABLED: SQL Analytics is not supported ..., which is 404 response to POST request.
@nfx nfx added this to the v0.3.2 milestone Mar 27, 2021
@nfx nfx self-assigned this Apr 1, 2021
@nfx
Copy link
Contributor Author

nfx commented Apr 1, 2021

this one is actually a duplicate of #564

@nfx nfx closed this as completed Apr 1, 2021
nfx added a commit that referenced this issue Apr 1, 2021
@nfx
Handle HTTP 404 on create as a proper error
99ecc23 
* 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 #564 #576
@nfx nfx mentioned this issue Apr 1, 2021
Merged
nfx added a commit that referenced this issue Apr 1, 2021
@nfx
Handle HTTP 404 on create as a proper error
5121dfc 
* 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 #564 #576
michael-berk pushed a commit to michael-berk/terraform-provider-databricks that referenced this issue Feb 15, 2023
@nfx
Handle HTTP 404 on create as a proper error
943a98b 
* 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
Assignees

@nfx nfx

Labels
None yet
Projects
None yet
Milestone
v0.3.2
Development

No branches or pull requests
1 participant
@nfx