magodo
@dwilson-daviesgroup Could you tell which version of the aztfexport you were using, and the CLI you were running?
@dwilson-daviesgroup Just want to check if you still have issue with this, or I can close it now?
: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.
@rrmistry Thank you for raising this! This is a fair feature request, while to be honest, we are not going to support property level features, as that will become hard...
Relating to https://github.com/magodo/tfadd/pull/8
@stemaMSFT The latest release of `aztfexport` pins to v3.77.0 of the provider (see https://github.com/Azure/aztfexport/releases/tag/v0.14.0). Whilst the `PowerShell72` is supported in v3.86.0 (see https://github.com/hashicorp/terraform-provider-azurerm/pull/23980). @msetogecko Before we create a new release...
This should have been fixed in the latest release v0.14.2.
You can use the "--non-interactive" option: https://learn.microsoft.com/en-us/azure/developer/terraform/azure-export-for-terraform/export-terraform-concepts#non-interactive-mode
: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.
Hi @Radamonas, by default the tool will ignore "zero" values or O(ptional)+C(omputed) properties, since the [goal](https://github.com/Azure/aztfexport#goal) of aztfexport is to generate valid configuration and pass terraform plan, otherwise, they might...