Xu Wu
@zjalexander hi is there any update on this issue? looking forward to having this issue fixed asap.
there is another similar break change in the `runbook.GetCotent` from `2018-06-30` to `2019-06-01`. could you please forward this to the service team too? @zjalexander or should I raise another issue...
but we can not migrate to the new SDK package in the short term(or even in the long term)
@tombuildsstuff hashicorp/go-azure-sdk generated the same code by autorest, so [the line ](https://github.com/hashicorp/go-azure-sdk/blob/ff5f76c500abe991c7c13cc5e2e6574649f1c60f/resource-manager/automation/2019-06-01/dscconfiguration/method_getcontent_autorest.go#L64)`autorest.ByUnmarshallingJSON(&result.Model),` will always cause an error.
Hi, @rikunarhi-cloud2 thanks for your feedback! The Empty string value has been removed in azurerm 3.0. it's a document mistake and I have submitted a PR to fix the doc....
yes, the root source is the swagger broken. en... as for runbook resource, it [uses `stable/2018-06-30/runbook.json` in `2020-01-13-preview` Track 1 sdk]( https://github.com/Azure/azure-rest-api-specs/blob/55458b642a7cdc8dd9b2928942d13c6f076399bc/specification/automation/resource-manager/readme.md?plain=1#L231), so it is a kind of API upgrade...
yes, seems the service team will not revert this change because `azure-sdk-go-go` has released a Track2 SDK(which is compatible with this swagger) to replace the track1 SDK. As I know...
@manicminer Thanks for your work! The case here is when the response body is a single string, not structured data, Track1 and current pandora will try to `json.Unmarshal` the HTTP...
@katbyte Track2 replaced autorest with a new base layer, but it has new authentication and other features designed not working for azurerm.
@katbyte since the `hashicorp/go-azure-sdk`'s new base layer is not released, and the current generated code for `2019-06-01` still broken the process(as described before). so it's still needed to use both...