magodo
@LaskiBear You can use the environment variable in this case: `export ARM_SKIP_PROVIDER_REGISTRATION=true`
@EttienneScheepers Have you tried with the latest release (v0.6.0), where it should be smart enough to deduce those resource types by their ids for you?
@EttienneScheepers Could you please elaborate more about how you run the tool? Do you run it via `aztfy rg `? If so, could you please show me the screen that...
@EttienneScheepers It appears the version you used is prior to v0.6.0. Would you please double check the version? Meanwhile, could you please run `aztfy` with `AZTFY_LOG_PATH` set to a path...
: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.
The importing time depends on the Azure API speeds, including the ARM template export API and the GET API of each resource to be imported. The time consumed by aztfy...
Can we get a benchmark of ARM template exporting from somewhere? As I noticed it takes long time when exporting ARM template for a large resource group.
@stemaMSFT In this commit: https://github.com/Azure/aztfy/pull/166/commits/2dd05eebc83dfdd4b534f455fa7d486f7c64a203, I've export two env vars, which will make the provider to skip calling the expensive RP listing API, which can increase the performance a lot.
@stemaMSFT With this change, a previously import that needs about ~10min now can finish in ~1min.
@stemaMSFT This has already been merged in the main branch, with this can we close this issue for now?