[yashdotdev13]

Summary

Fixes [#709](#709) by propagating the Consul ACL token to event firing API calls.

Previously, the ACL token was not included when firing Consul events, causing requests to fail when ACL enforcement was enabled.

Changes

• Added ACL token support to ConsulBinderProperties.
• Enabled configuration properties binding in ConsulBinderConfiguration.
• Updated EventService to pass the ACL token when firing events.
• Updated ConsulSendingHandler to include the ACL token in outbound event messages.
• Added regression tests for ACL token propagation in EventService and ConsulSendingHandler.

Testing

• ./mvnw -pl spring-cloud-consul-binder -am test
• All tests passed.

Closes #709

[ryanjbaxter]

eventList should also pass the token. The tests should also cover eventList, the watch call, the default token, and property binding

[yashdotdev13]

Thanks for the feedback!

I have updated the implementation to propagate the ACL token to both the eventList and watch calls. I've also added tests covering ACL token propagation for fire, eventList, and watch operations.

The binder module tests are passing now. Please take another look when you get a chance.

[ryanjbaxter]

If this.properties.getAclToken() is an empty string I think we should return null as well to maintain the previous behavior

[yashdotdev13]

Thanks for pointing this out! I've made the change and added a test for it. All binder tests are passing now.