* add azapi support
* remove azurerm config when exporting to azapi
* code format and remove GenTFResources
* set only corresponding provider in provider config file
* format
* Stick on gosec v2.16.0
The now latest version v2.17.0 will cause error as below:
Golang errors in file: []:
> [line 0 : column 0] - error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
> [line 0 : column 0] - error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
> [line 0 : column 0] - error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
> [line 0 : column 0] - error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
This probably due to the fact that 2.17.0 updated its Go version, which might conflicts with the github action OS installed version.
* fix lint warnings
* PMC migration
* only try one repo
* Update
* Upgrade pyOpenSSL
* debug
* use cli to get key vault certificate
* update
* continue using keyvautl task
* typo
* Enable other deb distro/release
* Enable for the rhel8-amd64
* Enable other rpm distro/release
* Collect subscription id in telemetry
* Separating the error trace to 2, so that we only need to redacate the details
* Split aztfexport end error to 2
* Fix a minor bug in the effective cli arg
* New CLI options: `--use-environment-cred`, `--use-managed-identiy-cred` and `--use-azure-cli-cred` to allow users to explicitly choose auth method instead of the default auth chain
* test cases for the new cli options
* Integrate with terraform-client-go for hcl only mode to eliminate `terraform` binary
Integrate with terraform-client-go for hcl only mode to eliminate `terraform` binary. This improves the performance (quicker speed and lower footprint) of importing.
To use it, users have to explicitly specify a new hidden flag (`--tfclient-plugin-go`). This flag is hidden since it is not supposed for CLI users to use, but is meant to be used by module users who wants to get the benefit of performance improvement.
* New option: `--provider-version` to overwrite the provider version used for importing (other than using the bound version)
* Determine the provider version constraint under used if not specified