Changelog for 7.17.0 is missing a breaking change in the Filebeat config

[OvervCW]

I just upgraded Filebeat from 7.16.1 to 7.17.0 and it started failing to startup with the following message:

2022-06-24T15:26:54.345Z	INFO	instance/beat.go:497	filebeat stopped.
2022-06-24T15:26:54.345Z	ERROR	instance/beat.go:1014	Exiting: Failed to start crawler: starting input failed: error while initializing input: fail to unpack the kubernetes configuration: invalid logs_path defined for resource_type: container, valid value is `/var/log/containers/` accessing 'filebeat.inputs.0.processors.0.add_kubernetes_metadata' (source:'filebeat.yml')
Exiting: Failed to start crawler: starting input failed: error while initializing input: fail to unpack the kubernetes configuration: invalid logs_path defined for resource_type: container, valid value is `/var/log/containers/` accessing 'filebeat.inputs.0.processors.0.add_kubernetes_metadata' (source:'filebeat.yml')

This happened because my configuration used the path /var/log/containers instead of /var/log/containers/ (note the trailing slash):

filebeat.inputs:
  - type: container
    paths:
      - "/var/log/containers/*.log"
    processors:
      - add_kubernetes_metadata:
          default_indexers.enabled: false
          default_matchers.enabled: false
          indexers:
            - container:
          matchers:
            - logs_path:
                logs_path: "/var/log/containers"
                resource_type: "container"

This was a bit puzzling because this configuration has been working fine for a long time. I think that the validation added as part of #28868 should either be changed to tolerate paths without trailing slashes or the release notes for 7.17.0 should mention this as a breaking change.

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[OvervCW]

👍

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!