magodo
magodo
@stemaMSFT I've locally tested for a rg in batch mode, which has following resources: - azurerm_linux_virtual_machine.res-2 - azurerm_managed_disk.res-1 - azurerm_network_interface.res-3 - azurerm_network_security_group.res-13 - azurerm_network_security_group.res-4 - azurerm_network_security_rule.res-10 - azurerm_network_security_rule.res-11 - azurerm_network_security_rule.res-12...
@KlasPihl Thank you for submitting this! This is actually not a bug in `aztfy`, but an inconsistency between the provider behavior (only allows `Tcp` since v3.0) and the service behavior...
@HughPrince You can always use `ignore_changes` to suppress this diff.
@argeljoseph Use the path down to the property you want to ignore. Meanwhile, I've submit a PR to fix the upstream issue: https://github.com/hashicorp/terraform-provider-azurerm/pull/18799.
@argeljoseph It should be something like: ``` lifecycle { ignore_changes = [ security_rule.n.protocol, ] } ``` (Note that the `n` above should be replaced with the exact index of the...
@argeljoseph I just realized the `.n` doesn't work here as `security_rule` is a set rather than a list, which can't be indexed. If you want to ignore all security rules,...
@MohnJadden You can press enter and specify the resource address manually. If you are not sure about the correct resource type, just press ESC to quit the input mode and...
@MohnJadden As we haven't heard from you for a long while, I'm going to close this issue for now. Please feel free to reopen it you still have any question.
@bourbonfgiles The aztfy will remove everything (by default) in the output directory. The *.aztfyResourceMapping.json* is generated at the output directory, and will be removed at the next run. The correct...
@stemaMSFT Could you please try `aztfy rg --batch -m ".aztfyResourceMapping.json" stema-aztfy-demo`?