provider/openstack: Deprecating Instance Volume attribute #13062
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
volume
attribute requires a BlockStorage client to be mixed in with the Compute resource. Right now it's hard-coded for the v1 API.block_device
provides a wealth of volume attachment capabilities and strictly uses the Compute API.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 thatvolume
is missing.