-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
r/virtual_machine: switching over to the new Storage SDK #3838
Conversation
c6bb153
to
4954dfc
Compare
Ignoring some failing tests ('plan' is resolved, one's handled by #3842 and the others are Quota issues) - the tests pass: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
…an trying to parse the config This ensures that all Disks attached to the Virtual Machine should be deleted at deletion time should the user be opted into it. This also exposes the full (correctly cased/validated ID's) such that we can switch to using the new storage sdk
3e259fa
to
163d682
Compare
This has been released in version 1.32.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.32.0"
}
# ... other configuration ... |
Hi, what must be done to solve this TODO? :
In our use case we must import a VM into the Terraform state by 'terraform import ... ...' and this field is imported with NULL. Greetz, Josef |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
This PR contains a few things related to the new Storage SDK switch:
I believe this should fix #102