Feature consul tls discovery

[chc0618]

Background

We are using SmallRye Stork with Consul in production.
In our production environment, Consul is running with TLS enabled.

Currently, Stork Consul discovery does not support TLS configuration,
so we added SSL/TLS support and verified it in production.

What’s included

• Support TLS when discovery services to Consul
• Support configuration for:
  • trust-store-path (CA file)
  • trust-store-password
  • key-store-path (client certificate + private key)
  • key-store-password
  • verify-host (hostname verification)
  • acl-token (Consul ACL authentication)
• Backward compatible (non-TLS users are not affected)

Production status

✅ Already running in production.

Why this is useful

More and more users deploy Consul in secure (TLS) mode.
This change allows Stork to be used in secure enterprise environments.

[aureamunoz]

Great work, thank you very much for this.
We need also some tests to validate this.

[aureamunoz]

Thanks!
Could you please add some test to validate this feature?

[chc0618]

Thanks! Could you please add some test to validate this feature?

Sure, I will add the required tests.
Since this feature touches both Consul Discovery and Consul Registration, I plan to include:
1. Unit tests for the configuration parsing
2. Integration tests using a test Consul instance (with and without TLS)
3. Verification that the added attributes (ssl, trust-store, key-store, verify-host, acl-token) are correctly passed into the Vert.x HTTP client options.

I will push the test changes in the next update.