This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new property, lfh.connect.messaging.nats.ssl, to the application to support enabling and disabling tls connections to NATS. TLS connections are enabled by default and can be set explicitly by setting the property to "true" (case insensitive). Setting the property to any other value will disable the TLS connections from LFH to NATs.
I'm adding this in to support a project/pov that is executing within a secure enclave/environment. This setting allows us to get a baseline installation in place, prior to securing the environment.
I tested this change with the following compose configuration