magodo
Reopening this issue as I saw the hcl-lang do have handling of the `count` and `for_each`: https://github.com/hashicorp/hcl-lang/blob/f5c7d040b70fffe6d92da992408c0f8481bb260c/decoder/reference_origins.go#L131-L134
Kindly ping @jackofallops
This PR got updated per the change on the underlying SDK at: https://github.com/hashicorp/go-azure-sdk/pull/1221. Now it depends on another PR: https://github.com/hashicorp/go-azure-sdk/pull/1224.
@jackofallops Given https://github.com/hashicorp/terraform-provider-azurerm/pull/30254 is merged, this PR is now ready for review.
@juljaeg Since 1.11.2, instead of using the oidc token file path when running in ADO pipeline, you can follow https://developer.hashicorp.com/terraform/language/backend/azurerm#example-configuration-for-azure-devops to use the ADO Pipelines OIDC auth via OIDC Request...
`aztfexport map` is what you need, just make sure to move the mapping file to somewhere else to avoid it being overwritten.
This bug is being tracked in #2063, which I'm going to close this in favour of - would you mind subscribing to that issue for updates? Thanks!
@xianlin I've locally tested to export a `azurerm_route_table` with `aztfexport` v0.16.0, which by default uses the azurerm v4.16.0. By seeing you are using `--append`, may I ask if your existing...
Kindly ping @bflad
@jaredfholgate Fantastic! Thanks for updating this, it LGTM!