Update changelog for 2.19.0 (#373)

CHANGELOG.md

@@ -1,7 +1,26 @@
-## 2.18.0 (July 24, 2023)
+## 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](https://github.com/hashicorp/terraform-provider-consul/issues/369))
+* The `consul_config_entry_service_resolver` resource can now be used to manage a Service Resolver config entry ([#368](https://github.com/hashicorp/terraform-provider-consul/issues/368))
+* The `consul_config_entry_service_intentions` resource can now be used to manage a Service Intention config entry ([#367](https://github.com/hashicorp/terraform-provider-consul/issues/367))
+* The `consul_config_entry_service_defaults` resource can now be used to manage a Service Defaults config entry ([#366](https://github.com/hashicorp/terraform-provider-consul/issues/366))
+* The `consul_config_entry_service_splitter` resource can now be used to manage a Service Splitter config entry ([#364](https://github.com/hashicorp/terraform-provider-consul/issues/364))
+* The `consul_acl_role_policy_attachment` resource can be used to attach a policy to a role created outside the Terraform configuration ([#362](https://github.com/hashicorp/terraform-provider-consul/issues/362))
+* The `consul_acl_role` resource now supports templated policies ([#358](https://github.com/hashicorp/terraform-provider-consul/issues/358))
+* The `policies` argument of the `consul_acl_role` resource now accept both a policy ID and a policy name ([#363](https://github.com/hashicorp/terraform-provider-consul/issues/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](https://github.com/hashicorp/terraform-provider-consul/issues/361))
+
+
+## 2.18.0 (July 24, 2023)
+
+NEW FEATURES:
+
 * The provider can now use [Terraform Cloud Workload Identity](https://developer.hashicorp.com/terraform/cloud-docs/workspaces/dynamic-provider-credentials/workload-identity-tokens) to connect to Consul using the `use_terraform_cloud_workload_identity` argument in the provider configuration [[#342](https://github.com/hashicorp/terraform-provider-consul/issues/342)].
 * The `consul_config_entry` resource now supports the `jwt-provider` configuration entries [[#349](https://github.com/hashicorp/terraform-provider-consul/issues/349)].
 * The `consul_prepared_query` resource can now specify `targets` in their configuration [[#340](https://github.com/hashicorp/terraform-provider-consul/issues/340)].