Use correct variable for insecure tls connection #315
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The value of `icingadb_database_tls_insecure` is meant to be used in the IcingaDB config template if the variable is defined. Prior to this change the condition checked against `icingadb_database_tls_insecure` while the used value was `icingadb_database_insecure`. Both cases now refer to `icingadb_database_tls_insecure`. Fixes #302
Donien
deleted the
fix/302-icingadb-database-tls-insecure-variable-mismatch
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The value of
icingadb_database_tls_insecureis meant to be used in the IcingaDB config template if the variable is defined. Prior to this change the condition checked againsticingadb_database_tls_insecurewhile the used value wasicingadb_database_insecure.Both cases now refer to
icingadb_database_tls_insecure.Fixes #302