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

is_volume_attachement not avaliable #1066

Closed
lstadnik opened this issue Feb 4, 2020 · 3 comments
Closed

is_volume_attachement not avaliable #1066

lstadnik opened this issue Feb 4, 2020 · 3 comments
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure

Comments

@lstadnik
Copy link

lstadnik commented Feb 4, 2020

ibm_is_volume can not be used due to a lack of attachment functionality.

The basic attachment function for VPC gen1, gen2 needs to be added.

@hkantare
Copy link
Collaborator

hkantare commented Feb 5, 2020

You can use volume while provision of instance..
https://ibm-cloud.github.io/tf-ibm-docs/v1.1.0/r/is_instance.html
volumes attribute can be used to attach volumes.

@lstadnik
Copy link
Author

lstadnik commented Feb 7, 2020

Yes, volumes block section can be used. Most of the use case in project requires attaching and detaching volumes while vm is running. This basic functional is avaliable from web ui level, so i believe it can be added as attach/detach function in terraform as well in future.

Here example for Power servers works in that way

data "ibm_pi_instance_volumes" "ds_volumes" {
pi_instance_name = "volume_1"
pi_cloud_instance_id = "49fba6c9-23f8-40bc-9899-aca322ee7d5b"
}

@hkantare hkantare added the service/VPC Infrastructure Issues related to the VPC Infrastructure label Jan 5, 2021
@kavya498
Copy link
Collaborator

Closing this issue as support is available from 1.28.0 and above releases..
Please use latest provider..

Thanks..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants