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.