-
Notifications
You must be signed in to change notification settings - Fork 4.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
Changing osDisk.Name is not allowed #5689
Conversation
Bowbaq
commented
Feb 11, 2020
``` Error: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=<nil> Code="PropertyChangeNotAllowed" Message="Changing property 'osDisk.name' is not allowed." Target="osDisk.name" ```
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.
Hey @Bowbaq. I've just confirmed this and the change looks good but we'll want to update the documentation as well to say that changing this forces a new resource to be created. https://github.com/terraform-providers/terraform-provider-azurerm/blob/master/website/docs/r/virtual_machine.html.markdown
hi @Bowbaq Thanks for opening this PR. The The replacement resources (in this instance As such whilst I'd like to thank you for this contribution - since this resource is in a feature-frozen state (to ensure compatibility) I'm going to close this PR for the moment - however this is fixed in the superseded resources (since they only support Managed Disks. Thanks! |
Is there a timeline on 2.0? As best I can tell, it has been WIP for well over a year. In the meantime, it sounds like I'm stuck with either a buggy |
@Bowbaq keep an eye on the milestones page but very soon. Whilst these new resources are in an opt-in Beta (to allow for Schema changes if necessary) we've not needed/planned any changes to them besides a few bug fixes coming in 1.44 - as such they should be what's going live in 2.0 in the near future. |
I'm having trouble believing the milestone page, seeing as #2807 was opened over a year ago, and the 2.0.0 milestone shows 47% done, yet is due in 8 days. |
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! |