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.

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

provider/openstack: Deprecating Instance Volume attribute #13062

Merged

Conversation

jtopjian
Copy link
Contributor

@jtopjian jtopjian commented Mar 25, 2017

This commit deprecates the volume attribute in the
openstack_compute_instance_v2 resource. It's recommended to either
use the block_device attribute or the openstack_compute_volume_attach_v2
resource.

I've been planning to do this for quite a while now. There are a few good reasons for doing this:

  1. The volume attribute requires a BlockStorage client to be mixed in with the Compute resource. Right now it's hard-coded for the v1 API.
  2. block_device provides a wealth of volume attachment capabilities and strictly uses the Compute API.
  3. The openstack_compute_volume_attach_v2 resource has been around for a while now and has been reported to work as it should. It provides the flexibility and decoupled design that volume is missing.

This commit deprecates the volume attribute in the
openstack_compute_instance_v2 resource. It's recommended to either
use the block_device attribute or the openstack_compute_volume_attach_v2
resource.
@stack72
Copy link
Contributor

stack72 commented Mar 25, 2017

LGTM! :) Thanks

@stack72 stack72 merged commit de8e2d7 into hashicorp:master Mar 25, 2017
@ghost
Copy link

ghost commented Apr 15, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants