Skip to content

v0.10.0

Compare
Choose a tag to compare
@magodo magodo released this 03 Mar 09:05

0.10.0 (Mar 3, 2023)

BREAKING CHANGES

  • aztfy now depends on a pre-installed terraform executable that is located at $PATH. Also, the directory under UserCacheDir/aztfy used for caching the downloaded terraform is now not needed and can be safely deleted. (#347)
  • aztfy now by default will collect telemetry for identifying issues and areas for improvement (see https://github.com/Azure/aztfy#config). Users can opt out by running aztfy config set telemetry_enabled false (#360)
  • Create the output directory (specified by -o) if not exists (#364)

ENHANCEMENTS:

  • New option --log-level (#317)
  • New option --module-path to support appending to nested module (#322)
  • Interactive mode keybinding del be used for reverting skip (#326)
  • Performance improvement:
    • Parallelize resource mapping (aztft), discovering (azlist) (#340) and initialization for importing (#341)
    • When there is no base state given, state merging will not use tfmerge (#347)
    • Only run terraform show once when converting from state to config (#349)
    • Avoid terraform init for import workspaces when --dev-provider is specified (#350)
  • New command config [get|set|show] to manage aztfy config file, which is under $HOME/.aztfy/config.json (#360)
  • map mode allows to reference a resource mapping file in the output directory even when --overwrite is specified. Previously, that resource mapping file will also be cleaned during overwriting (#361)
  • Keep resource mapping file and skipped resource file in hcl only mode (#365)
  • Supporting terraform-provider-azurerm v3.46.0 (#369)

BUG FIXES:

  • Don't push state if there is no state to push (#327)
  • Keep resource order in the config as is in the import list (#329)
  • Fix --append leaks to be used together with --hcl-only in interactive mode (#363)

OTHERS:

  • Refactoring and exposing some useful type/func to pkg to be called by external Go modules. NOTE: There is no compatibility guarantee for these APIs. (#336, #346, #362)