v2.20.0

BUG FIXES:

• The consul_acl_role_policy_attachment resource no longer panic when given the UUID of a role that does not exist (#370 and #378).

NEW FEATURES:

• The consul_keys datasource now has a error_on_missing_keys argument that makes it possible to get an error when a key is absent from the KV store (#14 and #375).

v2.19.0

2.19.0 (October 25, 2023)

NEW FEATURES

• The consul_config_entry_service_router resource can now be used to manage a Service Router config entry (#369).
• The consul_config_entry_service_resolver resource can now be used to manage a Service Resolver config entry (#368).
• The consul_config_entry_service_intentions resource can now be used to manage a Service Intention config entry (#367).
• The consul_config_entry_service_defaults resource can now be used to manage a Service Defaults config entry (#366).
• The consul_config_entry_service_splitter resource can now be used to manage a Service Splitter config entry (#364).
• The consul_acl_role_policy_attachment resource can be used to attach a policy to a role created outside the Terraform configuration (#362).
• The consul_acl_token and consul_acl_role resource now supports templated policies (#358).
• The policies argument of the consul_acl_role resource now accept both a policy ID and a policy name (#363).

CHANGES:

• The consul_config_entry resource now ignore changes to the Status field for http-route, tcp-route and api-gateway config entries (#361)

v2.18.0

NEW FEATURES

• The provider can now use Terraform Cloud Workload Identity to connect to Consul using the use_terraform_cloud_workload_identity argument in the provider configuration [#342].
• The consul_config_entry resource now supports the jwt-provider configuration entries [#349].
• The consul_prepared_query resource can now specify targets in their configuration [#340].
• The consul_prepared_query resource can now specify remove_empty_tags in their configuration [#312].
• The consul_certificate_authority now supports the config_json argument to set complex configuration [#341].

CHANGES:

• The name argument of the consul_prepared_query resource is now optional [#312].
• The consul_acl_role now return an explicit error message if a policy is specified using its name instead of its ID [#345].

v2.17.0

CHANGES:

• The token argument in the resources and datasources has been deprecated. The token argument in the provider configuration should be used instead ([#332] and [#298]).

NEW FEATURES:

• The consul_config_entry datasource can now be used to read the configuration of a given config entry ([#318]).

IMPROVEMENTS:

• The consul_node resource can now be imported ([#323]).
• The consul_config_entry resource can now be imported ([Gh-319] and [#316]).
• The consul_peering resource has been updated to support the changes in Consul 1.14 ([#328]).
• The consul_peering, consul_peerings datasources have been updated to support the changes in Consul 1.14 ([#328]).
• The consul_config_entry resource now support the new peer parameters introduced in Consul 1.14 ([#328]).

v2.16.2

NEW FEATURES:

• The consul_peering and consul_peering_token resources can now be used to manage Consul Cluster Peering configuration (#309).
• The consul_peering and consul_peerings datasources can now be used to introspect Consul Cluster Peering configuration (#309).

IMPROVEMENTS:

• The consul_acl_token_secret_id datasource now supports reading tokens in a Consul Admin Partition (#315).

v2.16.1

NEW FEATURES:

• The consul_peering and consul_peering_token resources can now be used to manage Consul Cluster Peering configuration (#309).
• The consul_peering and consul_peerings datasources can now be used to introspect Consul Cluster Peering configuration (#309).

IMPROVEMENTS:

• The consul_acl_token_secret_id datasource now supports reading tokens in a Consul Admin Partition (#315).

v2.16.0

NEW FEATURES:

• The consul_peering and consul_peering_token resources can now be used to manage Consul Cluster Peering configuration (#309).
• The consul_peering and consul_peerings datasources can now be used to introspect Consul Cluster Peering configuration (#309).

IMPROVEMENTS:

• The consul_acl_token_secret_id datasource now supports reading tokens in a Consul Admin Partition (#315).

v2.15.1

BUG FIXES:

• The support of Admin Partition has been fixed for consul_config_entry: a new partition argument is now present and should be used instead of setting Partition in config_json.