magodo

@bflad One concern about changing these attributes from declarative to imperative manner is that makes the static analysis tools (e.g. tfproviderlint) hard to implement. What do you think about this?

@tmccombs FYI: https://github.com/apparentlymart/terrafy, especially you can checkout the https://github.com/apparentlymart/terrafy/blob/main/docs/quirks.md.

@pavan088 Thank you for submitting this! This appears to be an API issue rather than a provider bug: https://github.com/Azure/azure-rest-api-specs/issues/18815.

@yashvit Yes, modifying the names from the mapping file is the expected approach for now. Alternatively, if the resource list is not that long, you can also do it from...

@hguy In this case, you can use `--name-pattern`/`-p` to specify the pattern to something other than `res-*` to avoid name collision. Currently, `aztfy` is not smart enough to start the...

`--append-main` is not necessary as users can always append the content of `main.aztfy.tf` to `main.tf` by themselves. `--name-pattern-start-index` is what I've also thought about :)

@stemaMSFT We can expose an option `-parallelism` to allow users to change the parallelism, which defaults to 10. This would align with terraform's CLI.

@MrSimonC This is really weired.. The error occured when run `terraform state show`, after `terraform import` the resource group. Could you please manually do the import and state show by...

@MrSimonC Much appreaciated for above detailed information, which is quite useful! The error is from the `terraform show`, which actually implies that the provider under used by `aztfy` can't unmarshal...

What is the difference between the proposal and `terraform plan`?