-
Notifications
You must be signed in to change notification settings - Fork 384
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] Recreating VPC for workspace fails on apply #732
Comments
@steve148 Please do workspace update in multiple steps. E.g. create a second network, commit, apply. Then in the next commit/apply change the network. Then in the third commit/apply remove the older network. This is currently a limitation of the platform. Would you also be able to PR in the documentation bit about it? :) |
There's also somewhat related bug #649 |
steve148
changed the title
[ISSUE] Provider bug
[ISSUE] Recreating VPC for workspace fails on apply
Jul 20, 2021
Merged
michael-berk
pushed a commit
to michael-berk/terraform-provider-databricks
that referenced
this issue
Feb 15, 2023
This commit closes databricks#732
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Terraform Version
Terraform version 0.140
Provider version 0.34.0
Affected Resource(s)
Please list the resources as a list, for example:
Environment variable names
n/a
Terraform Configuration Files
Debug Output
n/a
Panic Output
n/a
Expected Behavior
The end goal was to change the CIDR block for the VPC. The plan showed the following for databricks related resources (minus the specific IDs).
Ideally, the new VPC and its subcomponents would have been created first, registered with the databricks workspace as the new network configuration, and then the old VPC and sub-components would have been cleaned up.
Actual Behavior
When running the plan, it failed with the following error.
I later found out this is because a workspace can have it's network configuration updated but not deleted (while the workspace is active).
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
The text was updated successfully, but these errors were encountered: