Releases: Azure/aztfexport
Releases · Azure/aztfexport
v0.8.0
0.8.0 (Oct 1, 2022)
BREAKING CHANGES:
- Changing the mapping file format (#234), also rename the file by removing its prefix dot (i.e. now
aztfyResourceMapping.json
) (#240) - The
-m
option inresource-group
mode is now replaced in favor of the newmap
subcommand (#241) - Renaming option
--batch
/-b
to--non-interactive
/-n
(#242) resource
subcommand now defaults to run interactively, to be consistent with the other 3 subcommands (#243)
ENHANCEMENTS:
- New subcommand:
query
to support customized set of resources (#231) - Removing dependency on ARM template export, together with the resource count limitation of 200 bound to ARM template, in
resource-group
mode (#231) - The cross resource dependency is now resolved by
aztfy
, rather than leveraging that from the ARM template, which gives precise dependencies than before (#231) - New file
aztfySkippedResources.txt
will now be generated to show the resources that are within the specified scope, but are skipped (#237) - Support property-like Terraform resources (a.k.a association/attachement resources). This also indicates that
resource
mode now might results into multiple Terraform resources. (#238) - New CLI option:
-g
/--generate-mapping-file
to just generate the resource mapping file and quit (#240) - New subcommand:
map
/mapping-file
to terrafy resources defined in a resource mapping file (#241) - New option:
--hcl-only
to only keep the .tf files in the output directory, and removing the other files (#246)
BUG FIXES:
- Fix data plane only resource id incorrectly prefixed by \ after mapping from azure id to TF id (#230)
v0.7.0
0.7.0 (Sep 13, 2022)
ENHANCEMENTS:
- Show import progress on rg batch mode (#188)
- Introduce
--type
in resource mode to allow users to explicitly set the TF resource type (#198) - New common option:
--full-properties
to generate full HCL from TF state. This is for inspection purpose, which means the config generated most likely requires modification to be valid (#210, #214) aztfy
now release Windowsmsi
in the github release. Meanwhile, corresponding Linux packages are published to https://packages.microsoft.com, which coversrhel8
,rhel9
,ubuntu-focal
andubuntu-jammy
repos (#204)
BUG FIXES:
v0.6.0
0.6.0 (Jul 21, 2022)
BREAKING CHANGES:
- The CLI is now refactored to two subcommands:
resource/res
andresource-group/rg
, where theresource/res
is to terrafy a single resource by its Azure resource ID, and theresource-group/rg
is to terrafy a resource group by name, as before (#166)
ENHANCEMENTS:
- New option:
--append
to allow importing to existing workspace (#151) - New subcommand
aztfy resource
to terrafy a single resource by its Azure resource ID (#166) - Replace the TF to Azure ID mapping by
aztft
, which makes the TF resource type auto deducing more accurate (#175) - Update provider schema to v3.14.0 (#176)
- UI improvement for non-interactive mode (#177)
BUG FIXES:
v0.5.0
0.5.0 (Jun 07, 2022)
ENHANCEMENTS:
- Conslidate the user resource mapping file (#107)
- CLI supports long form option and env var source (#111)
- Interactive filter (via /) supports regexp (#115)
- New shortcut key delete to mark items to be skipped (#116)
- Update schema and resource mapping for provider v3.9.0 (#126)
BUG FIXES:
- ID transformation for frontdoor (#120)
v0.4.0
0.4.0 (May 23, 2022)
ENHANCEMENTS:
- Update schema and resource mapping for v3.7.0 (#106)
- Batch mode now can be invoked without the resource mapping file (
-m
). In this case, only the resource types that can be automatically deduced byaztfy
will be imported (#103) - Switch the underlying SDK to Azure SDK Track2 (#87)
BUG FIXES:
v0.3.0
v0.2.0
0.2.0 (April 22, 2022)
ENHANCEMENTS:
- Removing the dependency on specific versions of
terraform
(i.e. v1.1 alpha versions) (#56)
Previously,aztfy
depends on an experimental feature ofterraform
calledterraform add
, which is only available in a transient period in its v1.1 alpha versions. This requirement is now not needed since this version, which means almost anyterraform
version works withaztfy
. - Schema and builtin resource mapping recommendation are generated for AzureRM provider v3.3.0 (#68)
v0.1.1
0.1.1 (April 6, 2022)
This patch release only makes some internal changes for the release pipeline. The only user facing change is that the Windows binaries are digitally signed. The checksum of the binaries for the other platforms are also signed, as before.