magodo

@cbellee Are these scope maps with underscores are created by the ACR by default? If so, then we should skip them to be generated via `aztfy`.

Hey @cbellee! Since I didn't hear from you for a while, I'm going to close this issue for now. If you still have questions, feel free to reopen.

@stemaMSFT I think the description of this issue doesn't match the title?

@ffribeiro In this case you can simply skip these two resources, as the SOA record is [modeled as a property of the `azurerm_dns_zone` in Terraform](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/dns_zone#soa_record), which means you only need...

@ffribeiro This is an unfortunate issue. What you need to do is to add up the missing `private_ip_address` in the two `azurerm_network_interface` resources. You can check the value via `terraform...

@ffribeiro There is a new CLI option called `--full-properties`, which can export all the non-computed-only attributes for the terrafied resources. That should solve your issues. But keep in mind in...

@MohnJadden When you are running the `aztfy` against a resource group, you already has the resource group name and the including subscription id? Then you can just use, e.g. `--name-pattern...

@pir8g33k Currently, the AzureRM provider doesn't support Powershell auth, it only supports Azure CLI auth and the others, please check https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#authenticating-to-azure for details.

:wave: Since we've not heard back here I'm going to close this issue for the moment. Feel free to reopen if still have questions.

@manjeetsinghcodz Thank you for submitting this! This is because currently `aztfy` is using the ARM template to do the resource listing and dependency resolvation. As seen from the error message,...