-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Feature Request]: Assign block storage to instance #360
Comments
Hi, I'm closing this, but feel free to reply if I misunderstood and we'll reopen this. |
Hi, thanks I'm aware of the functionality provided in the Thinking of circular dependencies, at least in our project, are harder to resolve if this functionality is only implemented in one direction. |
I'm not sure I understand, doesn't the fact that the functionality is not implemented in both directions prevent circular dependencies? Perhaps you can share more details about your use case to make this clearer? |
How does Terraform handle moving a volume from one instance to another without that? |
What feature would you like to have in the provider?
It would be nice to have the capability to attach the created volume to a specific instance or server.
e.g.
other providers for reference:
https://registry.terraform.io/providers/hetznercloud/hcloud/latest/docs/resources/volume#server_id
https://registry.terraform.io/providers/ionos-cloud/ionoscloud/latest/docs/resources/volume#server_id
The text was updated successfully, but these errors were encountered: