Releases: kbst/terraform-provider-kustomization
Releases · kbst/terraform-provider-kustomization
v0.7.2
v0.7.1
v0.7.0
Changelog
- Switch to new ID format as the default and enable in-place apiVersion upgrades #130 - thanks @willthames
- Improve error message when API group/kind is missing #144 - thanks @willthames
- Add patch options to support
allow_kind_change
andallow_name_change
#146 - thanks @willthames
v0.6.0
Changelog
- Replace homegrown caching RESTMapper with upstream implementation #105
- Add documentation for load-restrictor #120 - thanks @willthames
- Add in-cluster provider configuration option #122 - thanks @willthames
- Refactor resource IDs to not include apiVersion #128 - thanks @willthames
- ForceNew when name or namespace change without state ID change #133
- Update Kustomize dependency versions #134 - thanks @willthames
Upcoming ID format change
Note about the ID format change. This release includes a new ID format. For now, the legacy format is still used by default. But a future release will migrate to the new format as the default. The new format has the benefit, that it does not include the apiVersion
in the ID anymore, enabling the provider to handle apiVersion
updates to Kubernetes resources as in-place updates. With the legacy format an apiVersion
change would result in a destroy-and-recreate plan. Refer to #93 for more details.
To use the new format already now, set legacy_id_format = false
in the provider. To enforce keeping the legacy format, set legacy_id_format = true
explicitly. This is currently also the default.
v0.5.0
Changelog
- Exactly one of
kubeconfig_path
orkubeconfig_raw
is now required #103
Users need to update their configurations when upgrading to v0.5.0 or later. For convenience,kubeconfig_path
can be set using theKUBECONFIG_PATH
environment variable. - Determine the patch type based on the GVK and send correct patch #102
- Add option to disable kustomize load restrictions #101 - thanks @dreddick-home