You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #84serviceBuilder support custom tls options; it would be a good feature to be able to configure the library for system-wide TLS configurations
The description of the bug or the rationale of your proposal
The use case we'd like to address is providing the user with the ability to configure their services with custom TLS certificates for all serviceProxies that are created; we figured that providing environment variables with file paths (that should be mounted as files, e.g k8s configmaps/secrets) would be a good solution; if these variables are provided the library will read them at boot and provide all serviceBuilder invocation with the proper tls options.
Note: If a serviceBuilder provides specific tls options they should override the system wide
The text was updated successfully, but these errors were encountered:
The feauture or bug you are proposing
Since #84
serviceBuilder
support custom tls options; it would be a good feature to be able to configure the library for system-wide TLS configurationsThe description of the bug or the rationale of your proposal
The use case we'd like to address is providing the user with the ability to configure their services with custom TLS certificates for all serviceProxies that are created; we figured that providing environment variables with file paths (that should be mounted as files, e.g k8s configmaps/secrets) would be a good solution; if these variables are provided the library will read them at boot and provide all serviceBuilder invocation with the proper tls options.
Note: If a serviceBuilder provides specific tls options they should override the system wide
The text was updated successfully, but these errors were encountered: