-
Notifications
You must be signed in to change notification settings - Fork 671
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
ibm_is_instance adding a data volume there is no option to auto-delete #646
Comments
Bump on this issue https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storage-cli If CLI allows to do that believe that Terraform provider should also allow |
Bump. Somewhat critical for our work. |
@ErikEvenson We have not added support to auto-delete volume when instance is destroyed beacuse it makes difficult to maintain the state of volumes... Unlike IBM Cloud Cli terraform needs to maintain the state of each resource/datasource for its smooth execution. If one resource controls the behaviour of other resource then we will not have consistent or valid state information. |
@hkantare you are then assuming that the instance will be deleted eventually via Terraform. I think the ability to add the auto-delete should still be available, default to false and the documentation can offer up your reasoning above for not setting it to true and let the engineer decide to use it or not. |
Available in 1.21.0 |
Affected Resource(s)
Please list the resources as a list, for example:
Expected Behavior
The documentation does not indicate how to set the added volumes to automatically delete upon instance deletion.
The text was updated successfully, but these errors were encountered: