-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
[azurerm] Add os_type and image_uri in azurerm_virtual_machine #6553
Conversation
Hi @Erouan50 This looks good - I will add a test for this later Thanks for the hard work here! Paul |
Hi @stack72 Ok, you're welcome ! I hope it will help you. Good luck for the next steps ! Erouan |
@Erouan50 looks like this has already worked for someone so that was good news :) Thanks again P. |
doesn't seem to be working for me. i'm not sure if im using the field wrong: note: i am putting in the url to the vhd, but the documentation says it should be in the form publisherName:offer:skus:version. but i dont know how you would do that for a custom made one. here is my *.tf file
the error i am getting is:
which isnt much help |
Hi @MattFenner I guess our problem comes from your custom image. It should be in the same storage account of our virtual machine's storage. I advice you to create your storage account with an other tf file and copy your image when the storage account is created. |
oh i didnt realise it had to be in the same storage account. i was trying to keep it separate so i didnt delete it when i went terraform destroy @Erouan50 is there any way to get better error messages, the built in ones seem very unhelpful? |
Yes is not very useful... About the error messages, I guest when this issue #6526 will be close, they will be displayed correctly. Meanwhile, you can see all errors in audit log of your resource group from azure gui. |
Is that a limitation of the code in terraform or with ARM? @Erouan50 |
Hi @pearcec I would say it's actually both. Firstly, ARM should detect it, but secondly, TF should have supported it from the start :) This will be fixed when 0.7 lands soon! Paul |
@stack72 Looks like this was merged into 0.6.16. I can't get it to work I get the same issue even trying to use the same storage account. Looks like it was successful for some. Anyone have a working example? |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Fix #6372
Partial fix of #6526