-
Notifications
You must be signed in to change notification settings - Fork 160
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
Add huaweicloud_compute_volume_attach ordering capacity #3154
Comments
Thanks for raising this, but we can't control the order if you use There are 2 ways to achieve this:
|
Yea, I think that depends on would be great, however this was an example scenario, since this is a module I'd like to have it prepared for multiple disks, it can be two but also can be 10, 12 etc |
Unforturnately, |
any chance of changing terraform provider behavior to inform the "device" we would like to use within the OS ? like a property to attach it to slot 1,2..10 ? |
Actually, we have a device parameter on API side, but it's not ensure and has many limitations. Maybe you can ask for ECS guys to see more information about that. |
You can refer to this parameter, |
Current Terraform Version
Use-cases
When creating Terraform Modules for ECS instances, every now and then I have to use huaweicloud_compute_volume_attach to attach data disks to the VMs and usually I want this to be attached on a certain order e.g. Disk1 128Gb and Disk2 512 Gb, currently it's impossible to determine which order the disks will get attached to the VM.
Attempted Solutions
This is the code I'm currently using on my terraform module
Proposal
Please add a property to allow order control while attaching the disk to the vm
References
The text was updated successfully, but these errors were encountered: